complete_sales_task
Mark one of the caller's sales tasks/activities done (or reopen it with done=false). Stamps or clears the completion time; activity_id is required.
This record as markdown: /tools/com-meta-council-decision-intelligence/complete-sales-task.md
What complete_sales_task does on Meta Council
AI agents use complete_sales_task 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 |
|---|---|---|---|
done | boolean | — | Default true (complete). Pass false to reopen. |
activity_id | string | Yes |
Parameters from the server's own tool schema.
Why complete_sales_task is rated Medium
The tool creates or modifies data (task completion status and timestamps) reversibly. It does not execute external code or commands, does not delete data irreversibly, does not move money, and does not merely read. The 'done=false' parameter indicates the action is reversible (tasks can be reopened).
From the tool's definition Tool description states it 'Mark[s] one of the caller's sales tasks/activities done (or reopen it with done=false). Stamps or clears the completion time' — this modifies task status and completion timestamps, creating reversible changes to task state.
Attacks that exploit this kind of access
The rule that runs complete_sales_task 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 complete_sales_task, this is the rule to start with:
complete_sales_task 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 complete_sales_task call is checked against it from then on.
Questions about complete_sales_task
Mark one of the caller's sales tasks/activities done (or reopen it with done=false). Stamps or clears the completion time; activity_id is required. 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.
complete_sales_task accepts 2 parameters: done, activity_id. Required: activity_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 complete_sales_task: 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.
complete_sales_task 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 complete_sales_task 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 complete_sales_task. 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.
complete_sales_task 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