Search confirmation history logs with various filters and pagination
AI agents call search_logs to retrieve information from MCP-Confirm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves confirmation history logs using search filters and pagination. It queries existing data only and produces no side effects, modifications, deletions, or external operations. The tool fits the 'Read' category as it is a retrieval/query operation. Severity is low because logs contain no sensitive financial or destructive information by nature—they are audit records of user confirmations.
From the tool's definition Tool name 'search_logs' with description 'Search confirmation history logs with various filters and pagination' indicates querying/retrieving historical data without modification or side effects.
Attacks that exploit this kind of access
Search confirmation history logs with various filters and pagination. It is categorised as a Read tool in the MCP-Confirm MCP Server, which means it retrieves data without modifying state.
Register the MCP-Confirm MCP server in PolicyLayer and add a rule for search_logs: 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 MCP-Confirm. Nothing to install.
search_logs 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 search_logs 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 search_logs. 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.
search_logs is provided by the MCP-Confirm MCP server (mako10k/mcp-confirm). 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 →