Low Risk

get_change_impact

get_change_impact

How to control get_change_impact ↓

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

Low Risk

Even though get_change_impact 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.

Documented attack patterns abuse exactly the kind of access get_change_impact gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Codetree, and nothing reaches the server without passing your rules. This is the rule we recommend for get_change_impact:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_change_impact": {}
  }
}

get_change_impact is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Codetree — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_change_impact tool do? +

get_change_impact. It is categorised as a Read tool in the Codetree MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_change_impact? +

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

What risk level is get_change_impact? +

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

Can I rate-limit get_change_impact? +

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

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

get_change_impact is provided by the Codetree MCP server (thinkyminer/codetree). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codetree tool call.

Deterministic rules across all 23 Codetree tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

23 Codetree tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.