AI agents use set_risk_parameters to create or update resources in Mcp Pear — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Pear environment.
This tool creates or modifies risk parameters (stop-loss and take-profit thresholds) on trading positions, which is a reversible configuration change. While it does not directly execute trades or move capital, it alters position parameters that govern automated trading behavior. Classified as Write rather than Execute because it updates configuration rather than triggering immediate external operations.
From the tool's definition Tool name 'set_risk_parameters' and description 'Set or update stop-loss / take-profit on an existing Pear Protocol position' indicate modification of position parameters. The verb 'Set or update' confirms write operation.
Attacks that exploit this kind of access
Set or update stop-loss / take-profit on an existing Pear Protocol position. Each threshold has type (. It is categorised as a Write tool in the Mcp Pear MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Pear MCP server in PolicyLayer and add a rule for set_risk_parameters: 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 Mcp Pear. Nothing to install.
set_risk_parameters 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 set_risk_parameters 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 set_risk_parameters. 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.
set_risk_parameters is provided by the Mcp Pear MCP server (marvelnwachukwu/mcp-pear). 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 →