list_sales_tasks
List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts. Close one with complete_sales_task.
This record as markdown: /tools/com-meta-council-decision-intelligence/list-sales-tasks.md
What list_sales_tasks does on Meta Council
AI agents call list_sales_tasks 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.
Why list_sales_tasks is rated Low
This tool retrieves and queries task data with no side effects. It is a pure read operation that returns filtered/organized information about tasks belonging to the caller. The severity is low because retrieving task metadata poses minimal security risk even if misused by an agent.
From the tool's definition Tool lists open sales tasks with bucketing and counts; explicitly 'List the caller's open sales tasks' and 'ordered most-urgent-first'. No modification, deletion, or execution described.
Attacks that exploit this kind of access
The rule that runs list_sales_tasks 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_sales_tasks, this is the rule to start with:
list_sales_tasks 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 list_sales_tasks call is checked against it from then on.
Questions about list_sales_tasks
List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts. Close one with complete_sales_task. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
Register the Meta Council MCP server in PolicyLayer and add a rule for list_sales_tasks: 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.
list_sales_tasks 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 list_sales_tasks 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 list_sales_tasks. 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.
list_sales_tasks 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