Predict merge conflicts between two branches by analyzing Apex class changes, DML patterns, and metadata dependencies. Helps prevent deployment failures.
AI agents call predict_conflicts to retrieve information from Squirex Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool scans and compares metadata to provide conflict predictions, which is fundamentally a read operation with no side effects. It helps prevent failures through informational output rather than executing changes, running code, or modifying state. The low severity reflects that misuse would only affect the accuracy of conflict predictions, not actual deployments or data integrity.
From the tool's definition Tool performs analysis and prediction of merge conflicts by examining 'Apex class changes, DML patterns, and metadata dependencies' — this is querying and analyzing data without modifying anything. The verb 'Predict' indicates analysis rather than action.
Attacks that exploit this kind of access
Predict merge conflicts between two branches by analyzing Apex class changes, DML patterns, and metadata dependencies. Helps prevent deployment failures. It is categorised as a Read tool in the Squirex Dev MCP Server, which means it retrieves data without modifying state.
Register the Squirex Dev MCP server in PolicyLayer and add a rule for predict_conflicts: 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 Squirex Dev. Nothing to install.
predict_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the predict_conflicts 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 predict_conflicts. 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.
predict_conflicts is provided by the Squirex Dev MCP server (squirex-dev/squirex-mcp). 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 →