Probe a bounded list query against production. GET-only, capped page size.
AI agents call probe_list_query 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.
This tool performs read-only operations against a live API endpoint using GET requests. While it probes production, GET requests have no side effects and cannot modify, delete, or execute operations. The bounded/capped nature of the query further constrains potential impact. This is a standard Read category operation.
From the tool's definition Tool description explicitly states 'GET-only, capped page size' and 'Probe a bounded list query'. GET requests retrieve data without modification. The 'capped page size' restriction further limits blast radius.
Attacks that exploit this kind of access
Probe a bounded list query against production. GET-only, capped page size. 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 probe_list_query: 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.
probe_list_query 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 probe_list_query 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 probe_list_query. 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.
probe_list_query 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 →