Get information about available APIs and their endpoints
AI agents call get_api_info to retrieve information from Mcp Api Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns metadata about available APIs and their endpoints—a classic read operation with no side effects, no code execution, and no data modification. The verb 'Get information' explicitly denotes a query action. Severity is low because misuse would only expose API metadata, not trigger actual API calls or data changes.
From the tool's definition Tool name 'get_api_info' and description 'Get information about available APIs and their endpoints' indicate a retrieval/query operation with no modification or execution of external services.
Documented attack patterns abuse exactly the kind of access get_api_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Api Gateway, and nothing reaches the server without passing your rules. This is the rule we recommend for get_api_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_api_info": {}
}
}get_api_info 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.
Get information about available APIs and their endpoints. It is categorised as a Read tool in the Mcp Api Gateway MCP Server, which means it retrieves data without modifying state.
Register the Mcp Api Gateway MCP server in PolicyLayer and add a rule for get_api_info: 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 Api Gateway. Nothing to install.
get_api_info 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_info 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_info. 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_info is provided by the Mcp Api Gateway MCP server (rflpazini/mcp-api-gateway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Mcp Api Gateway tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Mcp Api Gateway tools catalogued and risk-classified — across an index of 42,500+ MCP servers.