Start with non-sensitive read operations only.
Tool safety
Grok Bot API tools safety checklist.
Before Grok can call your API through MCP, decide exactly which tools are safe, how auth is protected, and what should remain blocked. Sourced generates this report automatically from OpenAPI.
01Details
Allowlist first
Do not treat an empty allowlist as safe; for Grok, omitted or empty allowed_tools can mean broader exposure than intended.
Name tools from stable OpenAPI operationId values.
Keep internal/admin endpoints excluded unless the owner explicitly approves them.
02Details
Auth boundary
Keep API secrets in the MCP server environment or protected connector headers.
Never accept an API key as a tool parameter that the model can see in conversation.
Require HTTPS for authenticated remote MCP servers.
Block OAuth/OpenID Connect until callback URLs, token storage, refresh, scopes, and revocation are reviewed.
03Details
Operation risk
Sensitive reads include users, API keys, billing, tokens, secrets, and admin inventory.
Write operations create or update state and should be reviewed one by one.
Destructive operations delete, refund, cancel, rotate, revoke, transfer, or purge data and should be excluded by default.
Rate limits and idempotency behavior should be documented before enabling mutating tools.
04Outputs
Sourced-generated proof
agent-readiness.md summarizes the safety counts and blocking issues.
adapter.ir.json stores normalized operations, auth, schemas, and safety labels.
harness.tests/safety-assertions.mjs checks the manifest and default-enabled tools.
PR_PLAN.md records the exact files and human approval gates before any customer-owned repo write.