web_read_config_get
AI agents call web_read_config_get 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.
The tool appears to retrieve configuration data from the Legado Web API based on its name. Configuration reads have minimal security impact—they do not modify state, delete data, execute commands, or create financial obligations. The 'get' verb and lack of destructive language classify this as a Read operation with low severity.
From the tool's definition Tool name 'web_read_config_get' uses 'get' verb which indicates data retrieval. The 'config' subject suggests reading configuration settings without modification.
Documented attack patterns abuse exactly the kind of access web_read_config_get 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_get:
{
"version": "1",
"default": "deny",
"tools": {
"web_read_config_get": {}
}
}web_read_config_get 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.
web_read_config_get. 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 web_read_config_get: 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_get 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 web_read_config_get 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_get. 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_get 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.