Poll the status of a running ingestion job.
AI agents call memory_ingest_status to retrieve information from Eve Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of an existing ingestion process. Polling for status is a read-only operation with no side effects—it does not create, modify, delete, or execute actions. The low severity reflects minimal blast radius; misuse would only expose status metadata, not cause data loss or unauthorized modifications.
From the tool's definition Tool name 'memory_ingest_status' and description 'Poll the status of a running ingestion job' indicate a query operation that retrieves status information without modifying or deleting data.
Attacks that exploit this kind of access
Poll the status of a running ingestion job. It is categorised as a Read tool in the Eve Memory MCP Server, which means it retrieves data without modifying state.
Register the Eve Memory MCP server in PolicyLayer and add a rule for memory_ingest_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 Eve Memory. Nothing to install.
memory_ingest_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 memory_ingest_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 memory_ingest_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.
memory_ingest_status is provided by the Eve Memory MCP server (sherifkozman/eve-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 →