get_report_review_envelope

Read one owned frozen review record and source hash without rebuilding its definitions. No declaration or permission to share is inferred. Requires tickets:read.

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/get-report-review-envelope.md

WHAT IT DOES

What get_report_review_envelope does on Meta Council

AI agents call get_report_review_envelope 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
`envelope_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_report_review_envelope is rated Low

Even though get_report_review_envelope 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

RECOMMENDED RULE

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

get_report_review_envelope Allowed

get_report_review_envelope is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_report_review_envelope": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_report_review_envelope

What does the get_report_review_envelope tool do? +

Read one owned frozen review record and source hash without rebuilding its definitions. No declaration or permission to share is inferred. Requires tickets:read. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does get_report_review_envelope accept? +

get_report_review_envelope accepts 1 parameter: envelope_id. Required: envelope_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_report_review_envelope? +

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

What risk level is get_report_review_envelope? +

get_report_review_envelope is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_report_review_envelope? +

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

How do I block get_report_review_envelope completely? +

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

What MCP server provides get_report_review_envelope? +

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

KEEP EXPLORING

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

This server

All 280 Meta Council tools →

Across the catalogue

review_changes on MCP Server PR Pilot →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →