Planner tool that tells LLMs exactly which mtasa-docs tools to call next for a given task. Use this to enforce MCP-first workflows and avoid manual wiki scraping.
AI agents call recommend_doc_workflow to retrieve information from MTA:SA Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is a planning/advisory tool that reads the task context and returns recommendations about which documentation tools to call. It has no side effects, performs no writes, executes no code, and causes no destructive or financial actions. It purely outputs guidance, making it a Read category tool with low severity.
From the tool's definition 'Planner tool that tells LLMs exactly which mtasa-docs tools to call next for a given task' — it provides recommendations/instructions, does not modify or delete data
Attacks that exploit this kind of access
Planner tool that tells LLMs exactly which mtasa-docs tools to call next for a given task. Use this to enforce MCP-first workflows and avoid manual wiki scraping. It is categorised as a Read tool in the MTA:SA Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MTA:SA Documentation MCP Server MCP server in PolicyLayer and add a rule for recommend_doc_workflow: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MTA:SA Documentation MCP Server. Nothing to install.
recommend_doc_workflow is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the recommend_doc_workflow rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for recommend_doc_workflow. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
recommend_doc_workflow is provided by the MTA:SA Documentation MCP Server MCP server (mtasa-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →