Find relevant progress entries by query, tags, or date range. Use to discover prior work before starting new tasks or when context is needed.
AI agents call search_logs to retrieve information from Agent Progress Tracker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
search_logs is a retrieval tool that queries stored progress entries without creating, modifying, or deleting data. It has no side effects beyond returning information. While it accesses a persistent SQLite database, the operation itself is read-only. The severity is low because misuse would at worst expose already-stored progress information, with no destructive or operational consequences.
From the tool's definition Tool description explicitly states 'Find relevant progress entries by query' and 'Use to discover prior work' — these are query and retrieval operations with no modification or deletion capability.
Attacks that exploit this kind of access
Find relevant progress entries by query, tags, or date range. Use to discover prior work before starting new tasks or when context is needed. It is categorised as a Read tool in the Agent Progress Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agent Progress Tracker MCP Server 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 Agent Progress Tracker MCP Server. 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 Agent Progress Tracker MCP Server MCP server (thesammykins/context-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 →