Check whether the Legado Web service is reachable.
AI agents call legado_ping 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 only performs a diagnostic query (ping) to verify service availability. It retrieves status information without creating, modifying, deleting, or executing any operations on the underlying system or data. This is a read-only, non-destructive operation with minimal blast radius.
From the tool's definition Tool name 'legado_ping' and description 'Check whether the Legado Web service is reachable' indicate a simple connectivity check with no side effects.
Documented attack patterns abuse exactly the kind of access legado_ping 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_ping:
{
"version": "1",
"default": "deny",
"tools": {
"legado_ping": {}
}
}legado_ping 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.
Check whether the Legado Web service is reachable. 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_ping: 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_ping 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_ping 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_ping. 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_ping 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.