Get temporal statistics about your memories. Shows distribution over time,
AI agents call get_temporal_stats 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 retrieves and presents temporal statistics and distribution patterns from existing memory data. It is purely informational with no side effects—it neither modifies data (Write), deletes data (Destructive), executes external operations (Execute), nor involves financial transactions (Financial).
From the tool's definition Tool name 'get_temporal_stats' and description 'Get temporal statistics about your memories. Shows distribution over time' indicates a retrieval operation that queries and displays aggregated data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get temporal statistics about your memories. Shows distribution over time,. 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 get_temporal_stats: 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.
get_temporal_stats 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 get_temporal_stats 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 get_temporal_stats. 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.
get_temporal_stats 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 →