submit_meta_council_feedback

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 51 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/submit-meta-council-feedback.md

WHAT IT DOES

What submit_meta_council_feedback does on Meta Council

AI agents use submit_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
`body`	string	—
`title`	string	Yes
`context`	object	—	Machine context: tool name, session id, model, timings.
`category`	string	—
`severity`	string	—

Parameters from the server's own tool schema.

RISK

Why submit_meta_council_feedback is rated Medium

An AI agent can call submit_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 signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_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 submit_meta_council_feedback, this is the rule to start with:

submit_meta_council_feedback Rate-limited

submit_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_meta_council_feedback": {
      "limits": [
        {
          "counter": "submit_meta_council_feedback_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every submit_meta_council_feedback call is checked against it from then on.

FAQ

Questions about submit_meta_council_feedback

What does the submit_meta_council_feedback tool do? +

Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface. Platform feedback only: do NOT use this for anything about your own business, customers, deals, invoices, or other data Meta Council manages on your behalf — use the relevant business tool for that instead (e.g. create_deal, create_invoice). Use it the moment a tool result, council run, or workflow falls short. Stored per-user and visible only to platform admins — the response returns an id + acknowledgement and submissions cannot be read back. Include machine context (tool name, session id, model) in the context object. 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 submit_meta_council_feedback accept? +

submit_meta_council_feedback accepts 5 parameters: body, title, context, category, severity. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_meta_council_feedback? +

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

What risk level is submit_meta_council_feedback? +

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

Can I rate-limit submit_meta_council_feedback? +

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

How do I block submit_meta_council_feedback completely? +

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

What MCP server provides submit_meta_council_feedback? +

submit_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.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →