[Host] Archive closed meeting. Read-only after.
AI agents use archive_meeting to create or update resources in N2n Nexus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your N2n Nexus environment.
This tool modifies meeting state by transitioning a closed meeting into an archived (read-only) form. While archiving is typically reversible in modern systems (data is preserved, not deleted), the operation itself is a state change that affects how the meeting can be accessed and used.
From the tool's definition Tool description states 'Archive closed meeting' which creates a new archived state of the meeting data, making it 'read-only after.' This is a modification operation that changes the meeting's status irreversibly from active to archived.
Documented attack patterns abuse exactly the kind of access archive_meeting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N2n Nexus, and nothing reaches the server without passing your rules. This is the rule we recommend for archive_meeting:
{
"version": "1",
"default": "deny",
"tools": {
"archive_meeting": {
"limits": [
{
"counter": "archive_meeting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_meeting 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.
Free to start. No card required.
[Host] Archive closed meeting. Read-only after. It is categorised as a Write tool in the N2n Nexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the N2n Nexus MCP server in PolicyLayer and add a rule for archive_meeting: 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 N2n Nexus. Nothing to install.
archive_meeting 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 archive_meeting 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 archive_meeting. 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.
archive_meeting is provided by the N2n Nexus MCP server (n2ns/n2n-nexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N2n Nexus, 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.
22 N2n Nexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.