reject_ingest_item
Rejects a research ingest item without touching normal memory.
This record as markdown: /tools/mapi-agent-memory/reject-ingest-item.md
What reject_ingest_item does on Mapi Agent Memory
AI agents use reject_ingest_item to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why reject_ingest_item is rated Medium
This tool modifies the state of an ingest item (transitions it to rejected status) but does so reversibly and without deleting or destructively affecting data. The rejection is a state change rather than deletion, and can likely be undone or re-ingested. It does not execute arbitrary code, move money, or permanently destroy data. This qualifies as a Write operation.
From the tool's definition Tool name is 'reject_ingest_item' which performs a rejection action on an ingest item. Description states it 'Rejects a research ingest item' — this modifies state (marks item as rejected) reversibly without touching normal memory, indicating a write…
Attacks that exploit this kind of access
The rule that runs reject_ingest_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reject_ingest_item, this is the rule to start with:
reject_ingest_item stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every reject_ingest_item call is checked against it from then on.
Questions about reject_ingest_item
Rejects a research ingest item without touching normal memory. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for reject_ingest_item: 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 Mapi Agent Memory. Nothing to install.
reject_ingest_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reject_ingest_item 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 reject_ingest_item. 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.
reject_ingest_item is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue