get_deal
Fetch one of the caller's deals by id with its full activity timeline (notes, calls, meetings, emails, tasks; newest first).
This record as markdown: /tools/com-meta-council-decision-intelligence/get-deal.md
What get_deal does on Meta Council
AI agents call get_deal 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 |
|---|---|---|---|
deal_id | string | Yes | The deal id. |
Parameters from the server's own tool schema.
Why get_deal is rated Low
This tool retrieves deal data and associated activity metadata without modification, deletion, or external execution. It has minimal blast radius—an AI agent misusing it would access existing deal information the user is authorized to see, which is a low-risk Read operation.
From the tool's definition Tool name 'get_deal' and description 'Fetch one of the caller's deals by id with its full activity timeline' indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_deal 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_deal, this is the rule to start with:
get_deal 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_deal call is checked against it from then on.
Questions about get_deal
Fetch one of the caller's deals by id with its full activity timeline (notes, calls, meetings, emails, tasks; newest first). It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
get_deal accepts 1 parameter: deal_id. Required: deal_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_deal: 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_deal 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_deal 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_deal. 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_deal 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