local_transform · Mcp Ollama MCP: Risk & Policy

WHAT IT DOES

What local_transform does on Mcp Ollama

AI agents invoke local_transform to trigger actions in Mcp Ollama. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why local_transform needs a policy

Code transformation tools execute logic that rewrites source code based on patterns. While reversible (Write-category), the execution of arbitrary transformation patterns against code files with unknown scope and validation represents an Execute risk: the tool runs pattern-matching logic whose effects depend on the code supplied and patterns applied.

From the tool's definition Tool performs 'mechanical code transformations' on code—pattern-based transforms that modify source files. The verb 'transform' combined with code modification capability indicates code execution and alteration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

local_transform Rate-limited

local_transform stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "local_transform": {
      "limits": [
        {
          "counter": "local_transform_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Ollama, so you can run agents against it safely.

FAQ

Questions about local_transform

What does the local_transform tool do? +

Perform mechanical code transformations locally. These are pattern-based transforms that don. It is categorised as a Execute tool in the Mcp Ollama MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on local_transform? +

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

What risk level is local_transform? +

local_transform is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit local_transform? +

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

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

local_transform is provided by the Mcp Ollama MCP server (true-alter/mcp-ollama). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.