Execute a GET-only read plan against production to validate a knowledge-layer recommendation.
AI agents call execute_read_plan to retrieve information from Weclapp Api Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is explicitly described as GET-only, meaning it only retrieves data without side effects. However, it operates against a production environment, which raises the severity to medium since misconfiguration or unintended queries against production could expose sensitive data or cause unintended load.
From the tool's definition 'Execute a GET-only read plan' and 'validate a knowledge-layer recommendation' — explicitly restricted to GET-only operations against production
Attacks that exploit this kind of access
Execute a GET-only read plan against production to validate a knowledge-layer recommendation. It is categorised as a Read tool in the Weclapp Api Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Weclapp Api Knowledge MCP server in PolicyLayer and add a rule for execute_read_plan: 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 Weclapp Api Knowledge. Nothing to install.
execute_read_plan 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 execute_read_plan 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 execute_read_plan. 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.
execute_read_plan is provided by the Weclapp Api Knowledge MCP server (serenmind/weclapp-api-knowledgebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →