Low Risk

get_stable_corridors

Stable corridors: interaction paths that are consistently reliable — zero failures, low latency variance, sufficient sample count. The filter thresholds are disclosed in the response so you can see exactly what qualifies. Useful for identifying which targets you can rely on.

Part of the ACR — Agent Composition Records MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_stable_corridors to retrieve information from ACR — Agent Composition Records without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_stable_corridors only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

acr-agent-composition-records.yaml
tools:
  get_stable_corridors:
    rules:
      - action: allow

See the full ACR — Agent Composition Records policy for all 25 tools.

Tool Name get_stable_corridors
Category Read
Risk Level Low

View all 25 tools →

Agents calling read-class tools like get_stable_corridors have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the get_stable_corridors tool do? +

Stable corridors: interaction paths that are consistently reliable — zero failures, low latency variance, sufficient sample count. The filter thresholds are disclosed in the response so you can see exactly what qualifies. Useful for identifying which targets you can rely on.. It is categorised as a Read tool in the ACR — Agent Composition Records MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_stable_corridors? +

Add a rule in your Intercept YAML policy under the tools section for get_stable_corridors. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ACR — Agent Composition Records MCP server.

What risk level is get_stable_corridors? +

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

Can I rate-limit get_stable_corridors? +

Yes. Add a rate_limit block to the get_stable_corridors rule in your Intercept 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_stable_corridors completely? +

Set action: deny in the Intercept policy for get_stable_corridors. 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_stable_corridors? +

get_stable_corridors is provided by the ACR — Agent Composition Records MCP server (@tethral/acr-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ACR — Agent Composition Records

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.