AI agents use book_add_local to create or update resources in Legado — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Legado environment.
Without explicit description, the 'add' operation combined with the local-data-management context suggests this tool creates or imports a new book entry into the Legado system. This is a reversible Write operation (the book can be removed or modified later).
From the tool's definition Tool name 'book_add_local' suggests creating or importing a book locally; sibling tools include 'book_save' (Write), 'book_delete' (Destructive), and 'book_search' (Read), indicating this server manages book data.
Documented attack patterns abuse exactly the kind of access book_add_local 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_add_local:
{
"version": "1",
"default": "deny",
"tools": {
"book_add_local": {
"limits": [
{
"counter": "book_add_local_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}book_add_local stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
book_add_local. It is categorised as a Write tool in the Legado MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Legado MCP server in PolicyLayer and add a rule for book_add_local: 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_add_local is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the book_add_local 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_add_local. 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_add_local 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.