crm_set_ai_summary
Set the AI-generated summary and/or next-action for a contact, company, or deal. These live in dedicated columns so agents do not pollute the human-edited description.
This record as markdown: /tools/com-getmunin-munin/crm-set-ai-summary.md
What crm_set_ai_summary does on Munin
AI agents use crm_set_ai_summary to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why crm_set_ai_summary is rated Medium
This tool creates or modifies CRM records (contact, company, or deal summaries and next-actions) without deleting or destroying data. The changes are reversible—an AI-generated summary can be overwritten or cleared. While this affects customer relationship data, it does not execute arbitrary code, destroy data irreversibly, or involve financial transactions.
From the tool's definition Tool description states it 'Set[s] the AI-generated summary and/or next-action for a contact, company, or deal', which creates or modifies data fields in a CRM system.
Attacks that exploit this kind of access
The rule that runs crm_set_ai_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_set_ai_summary, this is the rule to start with:
crm_set_ai_summary 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 Munin, apply this rule, and every crm_set_ai_summary call is checked against it from then on.
Questions about crm_set_ai_summary
Set the AI-generated summary and/or next-action for a contact, company, or deal. These live in dedicated columns so agents do not pollute the human-edited description. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for crm_set_ai_summary: 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 Munin. Nothing to install.
crm_set_ai_summary 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 crm_set_ai_summary 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 crm_set_ai_summary. 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.
crm_set_ai_summary is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue