add_validation_event
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/add-validation-event.md
What add_validation_event does on Mapi Agent Memory
AI agents use add_validation_event 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 add_validation_event is rated Medium
The 'add' prefix strongly indicates a Write operation (creates/modifies data reversibly). Given the server context of 'auditable memory and governance for AI agents,' this tool likely appends validation events to an audit log or memory store. While Write is the most defensible classification, the empty description prevents higher confidence.
From the tool's definition Tool name 'add_validation_event' suggests creating or recording a validation event. The verb 'add' combined with 'event' indicates a write operation that creates a new record or log entry.
Attacks that exploit this kind of access
The rule that runs add_validation_event 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 add_validation_event, this is the rule to start with:
add_validation_event 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 add_validation_event call is checked against it from then on.
Questions about add_validation_event
add_validation_event is a write tool on the Mapi Agent Memory MCP server. 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 add_validation_event: 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.
add_validation_event 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 add_validation_event 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 add_validation_event. 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.
add_validation_event 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