mark_email_sent
Record that a draft was sent (moves it into mail history with a sentAt timestamp). Does not actually send — tracking only.
This record as markdown: /tools/ai-featureboard-featureboard/mark-email-sent.md
What mark_email_sent does on FeatureBoard
AI agents use mark_email_sent 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 mark_email_sent is rated Medium
This tool creates or updates records reversibly (recording a sent status and timestamp on an existing draft). It does not delete data (ruling out Destructive), execute external operations (ruling out Execute), move money (ruling out Financial), or trigger side effects beyond state modification.
From the tool's definition 'Record that a draft was sent' and 'moves it into mail history with a sentAt timestamp' indicate the tool modifies state by updating a record (adding a sentAt timestamp and relocating a draft).
Attacks that exploit this kind of access
The rule that runs mark_email_sent 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 mark_email_sent, this is the rule to start with:
mark_email_sent 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 mark_email_sent call is checked against it from then on.
Questions about mark_email_sent
Record that a draft was sent (moves it into mail history with a sentAt timestamp). Does not actually send — tracking only. 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 mark_email_sent: 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.
mark_email_sent 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 mark_email_sent 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 mark_email_sent. 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.
mark_email_sent 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