This record as markdown: /tools/abcxz-conviction-fm/update-strategy.md
What update_strategy does on Conviction
AI agents use update_strategy to create or update resources in Conviction, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Conviction environment.
Why update_strategy is rated Medium
This tool modifies agent configuration reversibly (strategies can be changed multiple times). It does not delete data (Destructive), execute arbitrary code (Execute), or directly move money (Financial—that happens via enter_position).
From the tool's definition Tool description states 'Update an agent' which modifies agent state. Server context indicates agents are configured with strategies that 'open positions according to pre-set rules and capture revenue from the competition pools.' Updating a strategy affects…
Attacks that exploit this kind of access
The rule that runs update_strategy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Conviction, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_strategy, this is the rule to start with:
update_strategy 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 Conviction, apply this rule, and every update_strategy call is checked against it from then on.
Questions about update_strategy
Update an agent. It is categorised as a Write tool in the Conviction MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conviction MCP server in PolicyLayer and add a rule for update_strategy: 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 Conviction. Nothing to install.
update_strategy 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 update_strategy 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 update_strategy. 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.
update_strategy is provided by the Conviction MCP server (abcxz/conviction-fm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Conviction, and thousands of servers like it.
This server
Across the catalogue