Mark notifications as read — either one specific notification (pass notification_id) or every currently-unread notification (omit notification_id). Use after triaging flowforge_list_notifications so unread_count reflects what's still outstanding.
Risk signalsBulk/mass operation — affects multiple targets
Part of the Flowforge server.
Free to start. No card required.
AI agents use flowforge_mark_notifications_read to create or modify resources in Flowforge. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call flowforge_mark_notifications_read repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Flowforge.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"flowforge_mark_notifications_read": {
"limits": [
{
"counter": "flowforge_mark_notifications_read_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Flowforge policy for all 49 tools.
These attack patterns abuse exactly the kind of access flowforge_mark_notifications_read gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark notifications as read — either one specific notification (pass notification_id) or every currently-unread notification (omit notification_id). Use after triaging flowforge_list_notifications so unread_count reflects what's still outstanding.. It is categorised as a Write tool in the Flowforge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flowforge MCP server in PolicyLayer and add a rule for flowforge_mark_notifications_read: 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 Flowforge. Nothing to install.
flowforge_mark_notifications_read 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 flowforge_mark_notifications_read 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 flowforge_mark_notifications_read. 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.
flowforge_mark_notifications_read is provided by the Flowforge MCP server (flowforge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 49 Flowforge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.