Get detailed instructions for using the Frappe API
AI agents call get_api_instructions to retrieve information from Frappe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only fetches and returns API documentation or instructions. It performs a read-only query operation with no capability to modify, delete, execute code, or affect data. The low severity reflects minimal blast radius if misused by an AI agent — the worst outcome would be an agent receiving redundant or confusing instructions.
From the tool's definition Tool name is 'get_api_instructions' and description states 'Get detailed instructions for using the Frappe API' — this retrieves documentation/instructional data with no side effects on Frappe application state.
Attacks that exploit this kind of access
Get detailed instructions for using the Frappe API. It is categorised as a Read tool in the Frappe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for get_api_instructions: 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 Frappe MCP Server. Nothing to install.
get_api_instructions 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 get_api_instructions 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 get_api_instructions. 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.
get_api_instructions is provided by the Frappe MCP Server MCP server (kiran-harbak/frappe_mcp_server). 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 →