generate_android_from_showdoc
AI agents invoke generate_android_from_showdoc to trigger actions in ShowDoc MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name and server context suggest it fetches API documentation and generates Android code (Entity classes, Repository patterns, Retrofit interfaces). Code generation involves reading data and writing/creating files, making Execute or Write the most appropriate category. Since it likely triggers a multi-step process (fetch + generate + write files), Execute is chosen.
From the tool's definition Tool name: generate_android_from_showdoc; server description: 'generates Android code including Entity classes, Repository patterns, and Retrofit interfaces'
Attacks that exploit this kind of access
generate_android_from_showdoc. It is categorised as a Execute tool in the ShowDoc MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ShowDoc MCP Server MCP server in PolicyLayer and add a rule for generate_android_from_showdoc: 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 ShowDoc MCP Server. Nothing to install.
generate_android_from_showdoc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_android_from_showdoc 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 generate_android_from_showdoc. 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.
generate_android_from_showdoc is provided by the ShowDoc MCP Server MCP server (yfcyfc123234/showdoc_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 →