Check the async processing status for a prior remember request.
AI agents call request_status to retrieve information from Evermemos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only checks the status of an asynchronous operation—a read-only query with no side effects. It retrieves information about a prior request state without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius if misused, as it cannot harm data or trigger unwanted operations.
From the tool's definition Tool name 'request_status' and description 'Check the async processing status for a prior remember request' indicate a query operation that retrieves status information without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access request_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Evermemos, and nothing reaches the server without passing your rules. This is the rule we recommend for request_status:
{
"version": "1",
"default": "deny",
"tools": {
"request_status": {}
}
}request_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the async processing status for a prior remember request. It is categorised as a Read tool in the Evermemos MCP Server, which means it retrieves data without modifying state.
Register the Evermemos MCP server in PolicyLayer and add a rule for request_status: 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 Evermemos. Nothing to install.
request_status 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 request_status 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 request_status. 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.
request_status is provided by the Evermemos MCP server (tt-a1i/evermemos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Evermemos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Evermemos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.