AI agents invoke replace_rule_test 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 testing a replace rule, which likely executes a rule against some input to validate behavior. This is an Execute action (running/testing a rule), but confidence is low due to empty description. It could also be Read (returning test results without side effects). Given the 'test' suffix, it most likely runs/executes a rule, so Execute is the most appropriate category.
From the tool's definition Tool name 'replace_rule_test' and server description mentions 'replace rules' management. Description is empty.
Documented attack patterns abuse exactly the kind of access replace_rule_test 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 replace_rule_test:
{
"version": "1",
"default": "deny",
"tools": {
"replace_rule_test": {
"limits": [
{
"counter": "replace_rule_test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}replace_rule_test 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.
replace_rule_test. 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 replace_rule_test: 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.
replace_rule_test 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 replace_rule_test 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 replace_rule_test. 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.
replace_rule_test 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.