New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

enable_attention_notification_rule

Explicitly enable the exact owned configuration and start a fresh observation cycle. Requires notifications:send plus independent human approval of actual destinations, fields, stages and quiet hours. No priority bypass. Reuse exact request_id for uncertainty; retrieve the receipt then read curre...

SERVERMeta Council SOURCEhttps://meta-council.com/mcp
Medium RISK CLASS
Category Write
Parameters 55 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/enable-attention-notification-rule.md

What enable_attention_notification_rule does on Meta Council

AI agents use enable_attention_notification_rule to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.

ParameterTypeRequiredDescription
rule_id string Yes
request_id string Yes
expected_revision integer Yes
acknowledge_delivery boolean Yes
expected_configuration_hash string Yes

Parameters from the server's own tool schema.

Why enable_attention_notification_rule is rated Medium

An AI agent can call enable_attention_notification_rule faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Questions about enable_attention_notification_rule

What does the enable_attention_notification_rule tool do? +

Explicitly enable the exact owned configuration and start a fresh observation cycle. Requires notifications:send plus independent human approval of actual destinations, fields, stages and quiet hours. No priority bypass. Reuse exact request_id for uncertainty; retrieve the receipt then read current state. May cause signed webhook notifications; never sends email. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does enable_attention_notification_rule accept? +

enable_attention_notification_rule accepts 5 parameters: rule_id, request_id, expected_revision, acknowledge_delivery, expected_configuration_hash. Required: rule_id, request_id, expected_revision, acknowledge_delivery, expected_configuration_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on enable_attention_notification_rule? +

Register the Meta Council MCP server in PolicyLayer and add a rule for enable_attention_notification_rule: 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.

What risk level is enable_attention_notification_rule? +

enable_attention_notification_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit enable_attention_notification_rule? +

Yes. Add a rate_limit block to the enable_attention_notification_rule 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.

How do I block enable_attention_notification_rule completely? +

Set action: deny in the PolicyLayer policy for enable_attention_notification_rule. 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.

What MCP server provides enable_attention_notification_rule? +

enable_attention_notification_rule 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Council's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.