Return the normalized summary of supported Legado HTTP and WS endpoints.
AI agents call legado_get_api_summary to retrieve information from Legado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available API endpoints—a read-only operation that retrieves metadata about the system without modifying, executing, or deleting anything. The blast radius of misuse is minimal; an AI agent obtaining endpoint information cannot cause harm beyond potential reconnaissance. Classified as Read with low severity.
From the tool's definition Tool name 'legado_get_api_summary' and description 'Return the normalized summary of supported Legado HTTP and WS endpoints' indicate a retrieval/query operation with no side effects. The verb 'Return' and noun 'summary' clearly describe data retrieval.
Documented attack patterns abuse exactly the kind of access legado_get_api_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Legado, and nothing reaches the server without passing your rules. This is the rule we recommend for legado_get_api_summary:
{
"version": "1",
"default": "deny",
"tools": {
"legado_get_api_summary": {}
}
}legado_get_api_summary 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.
Return the normalized summary of supported Legado HTTP and WS endpoints. It is categorised as a Read tool in the Legado MCP Server, which means it retrieves data without modifying state.
Register the Legado MCP server in PolicyLayer and add a rule for legado_get_api_summary: 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 Legado. Nothing to install.
legado_get_api_summary 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 legado_get_api_summary 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 legado_get_api_summary. 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.
legado_get_api_summary is provided by the Legado MCP server (joestar817/legado-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Legado, 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.
31 Legado tools catalogued and risk-classified — across an index of 43,000+ MCP servers.