streamline_rust_imports · Shell Executor MCP Server MCP

WHAT IT DOES

What streamline_rust_imports does on Shell Executor MCP Server

AI agents use streamline_rust_imports to create or update resources in Shell Executor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shell Executor MCP Server environment.

WHY IT NEEDS A POLICY

Why streamline_rust_imports needs a policy

This tool modifies source code files by reorganizing/consolidating Rust import statements. It changes existing code structure (Write category) but in a reversible, non-destructive way. The severity is medium because automated code modification could introduce errors or break builds if applied incorrectly, though the operation is targeted and limited to import statements.

From the tool's definition Streamline Rust import statements by consolidating imports with the same base path

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

streamline_rust_imports Rate-limited

streamline_rust_imports stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "streamline_rust_imports": {
      "limits": [
        {
          "counter": "streamline_rust_imports_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about streamline_rust_imports

What does the streamline_rust_imports tool do? +

Streamline Rust import statements by consolidating imports with the same base path. It is categorised as a Write tool in the Shell Executor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on streamline_rust_imports? +

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

What risk level is streamline_rust_imports? +

streamline_rust_imports is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit streamline_rust_imports? +

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

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

streamline_rust_imports is provided by the Shell Executor MCP Server MCP server (kosiew/zmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.