get_consulting_engagement
Get one owned engagement with its document revisions, milestones, and internal deliverables. Long document bodies are previewed.
This record as markdown: /tools/com-meta-council-decision-intelligence/get-consulting-engagement.md
What get_consulting_engagement does on Meta Council
AI agents call get_consulting_engagement 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 |
|---|---|---|---|
engagement_id | string | Yes |
Parameters from the server's own tool schema.
Why get_consulting_engagement is rated Low
This tool retrieves and queries consulting engagement data without modifying, executing external operations, or causing destructive effects. It is a straightforward read operation that returns consulting engagement information, document previews, and related metadata. The preview of long document bodies does not constitute a side effect.
From the tool's definition Tool description states 'Get one owned engagement' with retrieval of document revisions, milestones, and deliverables. The verb 'Get' and the absence of any modification, deletion, or execution language indicate read-only data retrieval.
Attacks that exploit this kind of access
The rule that runs get_consulting_engagement 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_consulting_engagement, this is the rule to start with:
get_consulting_engagement is read-only, so it stays allowed. 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 get_consulting_engagement call is checked against it from then on.
Questions about get_consulting_engagement
Get one owned engagement with its document revisions, milestones, and internal deliverables. Long document bodies are previewed. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_consulting_engagement accepts 1 parameter: engagement_id. Required: engagement_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 get_consulting_engagement: 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.
get_consulting_engagement is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_consulting_engagement 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 get_consulting_engagement. 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.
get_consulting_engagement 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