AI agents invoke book_source_debug to trigger actions in Legado. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name suggests a debugging operation against book sources, which likely involves executing diagnostic operations or triggering external requests to validate book sources. Debug operations in this context (Legado book sources) typically involve making network requests to test source configurations. The empty description lowers confidence.
From the tool's definition Tool name contains 'debug', server description mentions 'AI-assisted debugging and management of book sources'. Description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access book_source_debug 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 book_source_debug:
{
"version": "1",
"default": "deny",
"tools": {
"book_source_debug": {
"limits": [
{
"counter": "book_source_debug_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}book_source_debug stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
book_source_debug. It is categorised as a Execute tool in the Legado MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Legado MCP server in PolicyLayer and add a rule for book_source_debug: 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.
book_source_debug is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the book_source_debug 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 book_source_debug. 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.
book_source_debug 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.