list_consulting_engagements

List consulting engagements owned by the API-key account.

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

Low RISK CLASS

Category Read

Parameters 30 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/list-consulting-engagements.md

WHAT IT DOES

What list_consulting_engagements does on Meta Council

AI agents call list_consulting_engagements 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
`limit`	integer	—
`status`	string	—
`client_id`	string	—

Parameters from the server's own tool schema.

RISK

Why list_consulting_engagements is rated Low

This tool retrieves and queries existing consulting engagement records belonging to the authenticated account. It performs a read-only operation with no capability to create, modify, delete, or execute external actions. The blast radius is minimal—an agent could only enumerate existing engagements visible to that API key, which is a standard query operation.

From the tool's definition Tool name 'list_consulting_engagements' and description 'List consulting engagements owned by the API-key account' indicate a retrieval operation with no modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_consulting_engagements Allowed

list_consulting_engagements 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": {
    "list_consulting_engagements": {}
  }
}

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 list_consulting_engagements call is checked against it from then on.

FAQ

Questions about list_consulting_engagements

What does the list_consulting_engagements tool do? +

List consulting engagements owned by the API-key account. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.

What parameters does list_consulting_engagements accept? +

list_consulting_engagements accepts 3 parameters: limit, status, client_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_consulting_engagements? +

Register the Meta Council MCP server in PolicyLayer and add a rule for list_consulting_engagements: 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 list_consulting_engagements? +

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

Can I rate-limit list_consulting_engagements? +

Yes. Add a rate_limit block to the list_consulting_engagements 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 list_consulting_engagements completely? +

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

list_consulting_engagements 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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