triage_meta_council_feedback
ADMIN ONLY: triage a platform-feedback report — set its status and/or admin notes (requires an ADMIN_EMAILS account; everyone else gets a permission error). Get the full feedback id from list_meta_council_feedback.
This record as markdown: /tools/com-meta-council-decision-intelligence/triage-meta-council-feedback.md
What triage_meta_council_feedback does on Meta Council
AI agents use triage_meta_council_feedback 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
status | string | — | |
admin_notes | string | — | Triage notes; an empty string clears them. |
feedback_id | string | Yes | Full feedback UUID from list_meta_council_feedback. |
Parameters from the server's own tool schema.
Why triage_meta_council_feedback is rated Medium
An AI agent can call triage_meta_council_feedback 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.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs triage_meta_council_feedback 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 triage_meta_council_feedback, this is the rule to start with:
triage_meta_council_feedback 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 Meta Council, apply this rule, and every triage_meta_council_feedback call is checked against it from then on.
Questions about triage_meta_council_feedback
ADMIN ONLY: triage a platform-feedback report — set its status and/or admin notes (requires an ADMIN_EMAILS account; everyone else gets a permission error). Get the full feedback id from list_meta_council_feedback. 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.
triage_meta_council_feedback accepts 3 parameters: status, admin_notes, feedback_id. Required: feedback_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 triage_meta_council_feedback: 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.
triage_meta_council_feedback 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 triage_meta_council_feedback 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 triage_meta_council_feedback. 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.
triage_meta_council_feedback 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