Create a prospective trading plan that activates when conditions are met. Stores a rule-based plan in prospective memory. The plan stays active until triggered, expired, or manually cancelled. Args: trigger_type: Type of trigger (e.g. "market_condition", "drawdown", "time_based") trigge...
Part of the Tradememory Protocol MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_trading_plan to create or modify resources in Tradememory Protocol. 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 create_trading_plan repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Tradememory Protocol.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
create_trading_plan:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Tradememory Protocol policy for all 15 tools.
Agents calling write-class tools like create_trading_plan have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a prospective trading plan that activates when conditions are met. Stores a rule-based plan in prospective memory. The plan stays active until triggered, expired, or manually cancelled. Args: trigger_type: Type of trigger (e.g. "market_condition", "drawdown", "time_based") trigger_condition: JSON string describing when to trigger (e.g. '{"regime": "ranging"}') planned_action: JSON string describing what to do (e.g. '{"type": "skip_trade"}') reasoning: Why this plan was created expiry_days: Days until plan expires (default 30) priority: Priority 0-1, higher = checked first (default 0.5). It is categorised as a Write tool in the Tradememory Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for create_trading_plan. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tradememory Protocol MCP server.
create_trading_plan 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 create_trading_plan rule in your Intercept 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 Intercept policy for create_trading_plan. 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.
create_trading_plan is provided by the Tradememory Protocol MCP server (mnemox-ai/tradememory-protocol). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept