reconcile_attention_notification_delivery
Record an owner declaration received or cancel with a note and current expected_version. Original network outcome and recovery history remain immutable. This is an attestation, never a fabricated receipt or permission to send again. Requires notifications:manage.
This record as markdown: /tools/com-meta-council-decision-intelligence/reconcile-attention-notification-delivery.md
What reconcile_attention_notification_delivery does on Meta Council
AI agents call reconcile_attention_notification_delivery to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | Yes | |
decision | string | Yes | |
request_id | string | Yes | |
delivery_id | string | Yes | |
expected_version | integer | Yes |
Parameters from the server's own tool schema.
Why reconcile_attention_notification_delivery is rated Critical
An AI agent that decides to call reconcile_attention_notification_delivery doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meta Council is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs reconcile_attention_notification_delivery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reconcile_attention_notification_delivery, this is the rule to start with:
reconcile_attention_notification_delivery is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every reconcile_attention_notification_delivery call is checked against it from then on.
Questions about reconcile_attention_notification_delivery
Record an owner declaration received or cancel with a note and current expected_version. Original network outcome and recovery history remain immutable. This is an attestation, never a fabricated receipt or permission to send again. Requires notifications:manage. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
reconcile_attention_notification_delivery accepts 5 parameters: note, decision, request_id, delivery_id, expected_version. Required: note, decision, request_id, delivery_id, expected_version. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for reconcile_attention_notification_delivery: 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 Meta Council. Nothing to install.
reconcile_attention_notification_delivery is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reconcile_attention_notification_delivery 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 reconcile_attention_notification_delivery. 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.
reconcile_attention_notification_delivery is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue