add_crm_message
Add an incoming message to the CRM inbox (starts pending review). Useful for logging inbound emails/leads that need triage and approval.
This record as markdown: /tools/ai-featureboard-featureboard/add-crm-message.md
What add_crm_message does on FeatureBoard
AI agents use add_crm_message to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why add_crm_message is rated Medium
This tool creates or adds data to a CRM inbox (reversibly modifiable entries marked as 'pending review'). It does not delete, execute arbitrary code, trigger financial transactions, or irreversibly modify existing records. The severity is medium because misuse could spam the CRM with false leads or misdirected messages, requiring manual cleanup, but the data remains recoverable and modifiable.
From the tool's definition Tool description states 'Add an incoming message to the CRM inbox' and 'logging inbound emails/leads' — this creates new records in the CRM system.
Attacks that exploit this kind of access
The rule that runs add_crm_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_crm_message, this is the rule to start with:
add_crm_message 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 FeatureBoard, apply this rule, and every add_crm_message call is checked against it from then on.
Questions about add_crm_message
Add an incoming message to the CRM inbox (starts pending review). Useful for logging inbound emails/leads that need triage and approval. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for add_crm_message: 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 FeatureBoard. Nothing to install.
add_crm_message 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 add_crm_message 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 add_crm_message. 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.
add_crm_message is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue