New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

log_deal_activity

Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date. Pass deal_id and/or lead_id (each must be owned by the caller). type defaults to 'note'; for a task set type='task' and a due_date (YYYY-MM-DD). Tasks appear in list_sales_tasks.

SERVERMeta Council SOURCEhttps://meta-council.com/mcp
Medium RISK CLASS
Category Write
Parameters 70 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/log-deal-activity.md

What log_deal_activity does on Meta Council

AI agents use log_deal_activity 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.

ParameterTypeRequiredDescription
body string —
done boolean — Mark a task already done.
type string — note|call|meeting|email|task (default note).
deal_id string — Owned deal to attach to.
lead_id string — Owned lead to attach to.
subject string —
due_date string — ISO date YYYY-MM-DD (for tasks).

Parameters from the server's own tool schema.

Why log_deal_activity is rated Medium

This tool creates new records (notes, calls, meetings, emails, tasks) within the deal/lead management system. These are reversible modifications to a CRM database. While it modifies deal state, it does not execute external operations, delete data, or create financial obligations. The write action is bounded to activity logging on pre-existing deals/leads that the caller owns, making it Write rather than Execute.

From the tool's definition The tool creates or modifies data through logging activities: 'Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date.' It writes task entries that 'appear in list_sales_tasks' and accepts parameters like type,…

Risk signalsAccepts raw HTML/template content (body)

Questions about log_deal_activity

What does the log_deal_activity tool do? +

Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date. Pass deal_id and/or lead_id (each must be owned by the caller). type defaults to 'note'; for a task set type='task' and a due_date (YYYY-MM-DD). Tasks appear in list_sales_tasks. 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.

What parameters does log_deal_activity accept? +

log_deal_activity accepts 7 parameters: body, done, type, deal_id, lead_id, subject, due_date. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on log_deal_activity? +

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

log_deal_activity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_deal_activity? +

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

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

log_deal_activity 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meta Council's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.