Subscribe to trade event notifications via webhook or email. Get notified when trades change state.
AI agents use swarmtrade_subscribe_notifications to create or update resources in Swarmtrade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Swarmtrade environment.
This tool creates a subscription (webhook or email endpoint registration), which is a reversible write operation — it creates a new notification record/configuration. It does not move money, delete data, or execute code, but it does register an external callback that could be used to exfiltrate trade state changes if misused.
From the tool's definition Subscribe to trade event notifications via webhook or email
Attacks that exploit this kind of access
Subscribe to trade event notifications via webhook or email. Get notified when trades change state. It is categorised as a Write tool in the Swarmtrade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Swarmtrade MCP server in PolicyLayer and add a rule for swarmtrade_subscribe_notifications: 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 Swarmtrade. Nothing to install.
swarmtrade_subscribe_notifications 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 swarmtrade_subscribe_notifications 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 swarmtrade_subscribe_notifications. 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.
swarmtrade_subscribe_notifications is provided by the Swarmtrade MCP server (tjcrowley/swarmtrade). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →