web_read_config_save
AI agents use web_read_config_save 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.
The name suggests saving web read configuration, which is a Write operation. However, the description is empty and uninformative, so confidence is reduced. Based on sibling tools (book_save, book_save_progress) that follow a similar naming pattern for write operations, and the 'save' verb in the name, this is most likely a Write operation that modifies application configuration.
From the tool's definition Tool name 'web_read_config_save' — 'save' implies writing/modifying configuration data.
Documented attack patterns abuse exactly the kind of access web_read_config_save 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 web_read_config_save:
{
"version": "1",
"default": "deny",
"tools": {
"web_read_config_save": {
"limits": [
{
"counter": "web_read_config_save_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}web_read_config_save 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.
web_read_config_save. 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 web_read_config_save: 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.
web_read_config_save 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 web_read_config_save 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 web_read_config_save. 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.
web_read_config_save 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.