simulate_position_change

Simulate the effect of adding or removing collateral, or borrowing/repaying debt on a lending position. Returns the projected health factor and collateral/debt totals. Supports Aave V3 (default), Compound V3 (pass protocol: "compound-v3" + market Comet address), and Morpho Blue (pass protocol: "m...

Server VaultPilot MCP vaultpilot-mcp
Category Read
Risk class Low
Parameters 84 required

What simulate_position_change does on VaultPilot MCP

AI agents call simulate_position_change to retrieve information from VaultPilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
asset string Yes
chain string
action string Yes
market string
wallet string Yes
marketId string
protocol string
amountUsd number Yes

Parameters from the server's own tool schema.

Why simulate_position_change needs a policy

Even though simulate_position_change only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about simulate_position_change

What does the simulate_position_change tool do? +

Simulate the effect of adding or removing collateral, or borrowing/repaying debt on a lending position. Returns the projected health factor and collateral/debt totals. Supports Aave V3 (default), Compound V3 (pass protocol: "compound-v3" + market Comet address), and Morpho Blue (pass protocol: "morpho-blue" + marketId bytes32). No transaction is sent. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does simulate_position_change accept? +

simulate_position_change accepts 8 parameters: asset, chain, action, market, wallet, marketId, protocol, amountUsd. Required: asset, action, wallet, amountUsd. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on simulate_position_change? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for simulate_position_change: 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 VaultPilot MCP. Nothing to install.

What risk level is simulate_position_change? +

simulate_position_change is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit simulate_position_change? +

Yes. Add a rate_limit block to the simulate_position_change 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.

How do I block simulate_position_change completely? +

Set action: deny in the PolicyLayer policy for simulate_position_change. 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.

What MCP server provides simulate_position_change? +

simulate_position_change is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.