This record as markdown: /tools/io-github-heznpc-iconnect/flag-message.md
What flag_message does on Iconnect
AI agents use flag_message to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why flag_message is rated Medium
Flagging/unflagging an email modifies its metadata state reversibly — the flag can be toggled back. This is a Write operation with medium severity since it alters email state but does not delete or expose sensitive content.
From the tool's definition Flag or unflag an email message
Attacks that exploit this kind of access
The rule that runs flag_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For flag_message, this is the rule to start with:
flag_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 Iconnect, apply this rule, and every flag_message call is checked against it from then on.
Questions about flag_message
Flag or unflag an email message. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect MCP server in PolicyLayer and add a rule for flag_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 Iconnect. Nothing to install.
flag_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 flag_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 flag_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.
flag_message is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue