deploy_release_diff

Diff two release targets for a project.

Server Run402 kychee-com/run402
Category Read
Risk class Low
Parameters 00 required

What deploy_release_diff does on Run402

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

Why deploy_release_diff needs a policy

The tool compares two release targets and returns the differences. This is a read-only operation that retrieves and presents data without modifying, executing, or deleting anything. Severity is low since misuse would only expose release configuration details.

From the tool's definition 'Diff two release targets for a project' — diffing is a read/comparison operation with no side effects

Questions about deploy_release_diff

What does the deploy_release_diff tool do? +

Diff two release targets for a project. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on deploy_release_diff? +

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

What risk level is deploy_release_diff? +

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

Can I rate-limit deploy_release_diff? +

Yes. Add a rate_limit block to the deploy_release_diff 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 deploy_release_diff completely? +

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

deploy_release_diff is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.