Search memories with temporal reasoning. Finds relevant memories considering
AI agents call search_temporal to retrieve information from memro 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 or retrieves memory data based on temporal parameters. No modifications, deletions, code execution, or financial transactions occur. The operation is non-destructive and returns results without altering stored state. It falls squarely into the 'Read' category as a search/retrieval function.
From the tool's definition Tool name 'search_temporal' and description 'Search memories with temporal reasoning. Finds relevant memories' indicate a retrieval/query operation. The verb 'search' and 'finds' are read-only operations with no side effects.
Attacks that exploit this kind of access
Search memories with temporal reasoning. Finds relevant memories considering. It is categorised as a Read tool in the memro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the memro MCP Server MCP server in PolicyLayer and add a rule for search_temporal: 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 memro MCP Server. Nothing to install.
search_temporal 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_temporal 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_temporal. 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_temporal is provided by the memro MCP Server MCP server (memrohq/memro-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 →