add_contact
Add a contact (name, email, role, phone) to a company. Contact ids are unique within the company.
This record as markdown: /tools/ai-featureboard-featureboard/add-contact.md
What add_contact does on FeatureBoard
AI agents use add_contact 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_contact is rated Medium
This tool creates new contact records within a company, which is a reversible modification operation. It does not execute code, delete data, move money, or trigger external processes. The blast radius is minimal since contact creation in a project management/CRM context is a standard business operation with no destructive or financial impact. Confidence is high due to clear, unambiguous description.
From the tool's definition Tool description explicitly states 'Add a contact' with fields (name, email, role, phone), indicating creation of new data records.
Attacks that exploit this kind of access
The rule that runs add_contact 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_contact, this is the rule to start with:
add_contact 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_contact call is checked against it from then on.
Questions about add_contact
Add a contact (name, email, role, phone) to a company. Contact ids are unique within the company. 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_contact: 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_contact 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_contact 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_contact. 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_contact 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