API help tool that provides detailed documentation and examples for all API debugging tools. Use this to understand how to use api_debug, api_login, and api_config tools effectively
AI agents call api_help to retrieve information from MCP Project Standards Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays documentation/help content. It has no side effects, does not modify data, and cannot cause harm. It is purely informational, explaining how to use other tools.
From the tool's definition provides detailed documentation and examples for all API debugging tools
Documented attack patterns abuse exactly the kind of access api_help gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Standards Server, and nothing reaches the server without passing your rules. This is the rule we recommend for api_help:
{
"version": "1",
"default": "deny",
"tools": {
"api_help": {}
}
} api_help is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
API help tool that provides detailed documentation and examples for all API debugging tools. Use this to understand how to use api_debug, api_login, and api_config tools effectively. It is categorised as a Read tool in the MCP Project Standards Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Project Standards Server MCP server in PolicyLayer and add a rule for api_help: 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 MCP Project Standards Server. Nothing to install.
api_help 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 api_help 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 api_help. 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.
api_help is provided by the MCP Project Standards Server MCP server (liliangshan/mcp-server-project-standards). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Standards Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 MCP Project Standards Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.