Search past memory logs and commit history inside a specific spreadsheet by keyword.
AI agents call search_log_memory to retrieve information from ContextCore MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing data (memory logs and commit history) without creating, modifying, deleting, or executing any operations. The search functionality is purely informational. Severity is low because misuse would only expose or reveal existing information rather than causing harm, data loss, or external effects.
From the tool's definition Tool description states 'Search past memory logs and commit history inside a specific spreadsheet by keyword.' The verb 'search' and the operation of querying historical data indicate a read-only retrieval action with no side effects.
Attacks that exploit this kind of access
Search past memory logs and commit history inside a specific spreadsheet by keyword. It is categorised as a Read tool in the ContextCore MCP MCP Server, which means it retrieves data without modifying state.
Register the ContextCore MCP server in PolicyLayer and add a rule for search_log_memory: 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 ContextCore MCP. Nothing to install.
search_log_memory 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_log_memory 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_log_memory. 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_log_memory is provided by the ContextCore MCP server (rkpraveendev/contextcore-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 →