Get a specific run with its full conversation + audit log (steps: user_input, assistant_text, tool_call, tool_result, approval_request, approval_granted, error).
AI agents call wafle_agents_runs_get to retrieve information from wafle MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical data about agent runs, conversations, and audit logs. It has no side effects, does not modify any data, does not execute code or external operations, and does not involve financial transactions. It is a straightforward read operation with minimal blast radius if misused—an agent could retrieve audit logs, but cannot modify the platform or cause harm through retrieval alone.
From the tool's definition Tool name includes 'get' and description states it retrieves 'a specific run with its full conversation + audit log' — purely a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get a specific run with its full conversation + audit log (steps: user_input, assistant_text, tool_call, tool_result, approval_request, approval_granted, error). It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_agents_runs_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 wafle MCP server. Nothing to install.
wafle_agents_runs_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 wafle_agents_runs_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 wafle_agents_runs_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.
wafle_agents_runs_get is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →