export_report_review_envelope
Export one verified frozen review record as versioned JSON or CSV, accessible HTML or optional tagged PDF. Returns exact bytes as UTF-8 or PDF base64 with SHA-256. PDF dependency or glyph failures offer HTML fallback. No delivery, share or approval is created. Requires tickets:read.
This record as markdown: /tools/com-meta-council-decision-intelligence/export-report-review-envelope.md
What export_report_review_envelope does on Meta Council
AI agents use export_report_review_envelope 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 |
|---|---|---|---|
format | string | — | |
envelope_id | string | Yes |
Parameters from the server's own tool schema.
Why export_report_review_envelope is rated Medium
An AI agent can call export_report_review_envelope 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.
Attacks that exploit this kind of access
The rule that runs export_report_review_envelope 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 export_report_review_envelope, this is the rule to start with:
export_report_review_envelope 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 export_report_review_envelope call is checked against it from then on.
Questions about export_report_review_envelope
Export one verified frozen review record as versioned JSON or CSV, accessible HTML or optional tagged PDF. Returns exact bytes as UTF-8 or PDF base64 with SHA-256. PDF dependency or glyph failures offer HTML fallback. No delivery, share or approval is created. Requires tickets:read. 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.
export_report_review_envelope accepts 2 parameters: format, envelope_id. Required: envelope_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 export_report_review_envelope: 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.
export_report_review_envelope 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 export_report_review_envelope 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 export_report_review_envelope. 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.
export_report_review_envelope 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