keyway_inject_run · Keyway MCP Server MCP: Risk & Policy

WHAT IT DOES

What keyway_inject_run does on Keyway MCP Server

AI agents invoke keyway_inject_run to trigger actions in Keyway MCP Server. 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 keyway_inject_run needs a policy

This tool executes arbitrary commands (Execute category), which makes it a vehicle for running potentially harmful operations. While the tool itself is designed for secure credential injection, it still permits execution of any command passed to it, giving an AI agent the ability to run shell commands, scripts, or other external operations.

From the tool's definition Tool description states 'Run a command with Keyway secrets injected as environment variables.' The verb 'Run' combined with 'command' indicates code/command execution capability. The tool can execute arbitrary commands with secret credentials injected.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

keyway_inject_run Rate-limited

keyway_inject_run 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": {
    "keyway_inject_run": {
      "limits": [
        {
          "counter": "keyway_inject_run_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 Keyway MCP Server, so you can run agents against it safely.

FAQ

Questions about keyway_inject_run

What does the keyway_inject_run tool do? +

Run a command with Keyway secrets injected as environment variables. Secrets are only available to this command. It is categorised as a Execute tool in the Keyway MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on keyway_inject_run? +

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

What risk level is keyway_inject_run? +

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

Can I rate-limit keyway_inject_run? +

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

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

keyway_inject_run is provided by the Keyway MCP Server MCP server (keywaysh/keyway-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.