Send, read, or list Gas Town internal mail messages
AI agents use gt_mail to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
While the tool includes read and list operations (Read category), the primary capability of sending messages makes this a Write tool. Sending mail is a reversible but consequential action that modifies system state by creating new messages.
From the tool's definition Tool description states 'Send, read, or list Gas Town internal mail messages'. The 'send' capability creates new messages with side effects.
Attacks that exploit this kind of access
Send, read, or list Gas Town internal mail messages. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for gt_mail: 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 Claude Flow. Nothing to install.
gt_mail 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 gt_mail 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 gt_mail. 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.
gt_mail is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.