submit_consulting_deliverable
Submit an owned draft deliverable for internal review without publishing it.
This record as markdown: /tools/com-meta-council-decision-intelligence/submit-consulting-deliverable.md
What submit_consulting_deliverable does on Meta Council
AI agents use submit_consulting_deliverable 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 |
|---|---|---|---|
deliverable_id | string | Yes |
Parameters from the server's own tool schema.
Why submit_consulting_deliverable is rated Medium
This tool creates a submission record or modifies the state of a draft deliverable to enter a review workflow. It does not delete or irreversibly destroy data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). The internal-only nature and lack of publishing prevents it from being a pure Read operation.
From the tool's definition Tool description states 'Submit an owned draft deliverable for internal review without publishing it' — the verb 'submit' indicates creation or modification of a document's status/metadata.
Attacks that exploit this kind of access
The rule that runs submit_consulting_deliverable 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_consulting_deliverable, this is the rule to start with:
submit_consulting_deliverable 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 submit_consulting_deliverable call is checked against it from then on.
Questions about submit_consulting_deliverable
Submit an owned draft deliverable for internal review without publishing it. 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.
submit_consulting_deliverable accepts 1 parameter: deliverable_id. Required: deliverable_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 submit_consulting_deliverable: 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.
submit_consulting_deliverable 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 submit_consulting_deliverable 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 submit_consulting_deliverable. 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.
submit_consulting_deliverable 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