record_campaign_open
Record that a recipient opened a campaign (idempotent per recipient) — for when a mail connector or manual entry reports opens. Updates open-rate stats.
This record as markdown: /tools/ai-featureboard-featureboard/record-campaign-open.md
What record_campaign_open does on FeatureBoard
AI agents use record_campaign_open 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 record_campaign_open is rated Medium
This tool creates or updates campaign open records and associated statistics. While it modifies state, the operation is idempotent and reversible — opens can be unmarked, records can be corrected, and statistics can be recalculated. This is a standard Write operation typical of CRM/campaign tracking systems.
From the tool's definition Tool description states 'Record that a recipient opened a campaign' and 'Updates open-rate stats', indicating it modifies data (open records and statistics) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs record_campaign_open 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 record_campaign_open, this is the rule to start with:
record_campaign_open 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 record_campaign_open call is checked against it from then on.
Questions about record_campaign_open
Record that a recipient opened a campaign (idempotent per recipient) — for when a mail connector or manual entry reports opens. Updates open-rate stats. 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 record_campaign_open: 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.
record_campaign_open 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 record_campaign_open 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 record_campaign_open. 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.
record_campaign_open 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