get_project_attention_policy
Read one owned project's current override or owner-policy inheritance, effective policy and immutable project history. Archived projects retain authority. Page history with next_before_revision while has_more. Requires tickets:read; no state changes.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-project-attention-policy.md
What get_project_attention_policy does on Meta Council
AI agents call get_project_attention_policy to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
project_id | string | Yes | |
before_revision | integer | — |
Parameters from the server's own tool schema.
Why get_project_attention_policy is rated Low
Even though get_project_attention_policy only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_project_attention_policy 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 get_project_attention_policy, this is the rule to start with:
get_project_attention_policy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_project_attention_policy call is checked against it from then on.
Questions about get_project_attention_policy
Read one owned project's current override or owner-policy inheritance, effective policy and immutable project history. Archived projects retain authority. Page history with next_before_revision while has_more. Requires tickets:read; no state changes. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_project_attention_policy accepts 3 parameters: limit, project_id, before_revision. Required: project_id. 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 get_project_attention_policy: 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.
get_project_attention_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_project_attention_policy 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 get_project_attention_policy. 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.
get_project_attention_policy 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.
This server
Across the catalogue