run_with_creds

A execute tool on the MCP Framework Personal MCP server.

SERVERMCP Framework Personal SOURCEinggerman/mcps

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/run-with-creds.md

WHAT IT DOES

What run_with_creds does on MCP Framework Personal

AI agents invoke run_with_creds to trigger actions in MCP Framework Personal. 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.

RISK

Why run_with_creds is rated High

run_with_creds triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_with_creds safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_with_creds, this is the rule to start with:

run_with_creds Rate-limited

run_with_creds 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": {
    "run_with_creds": {
      "limits": [
        {
          "counter": "run_with_creds_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every run_with_creds call is checked against it from then on.

FAQ

Questions about run_with_creds

What does the run_with_creds tool do? +

run_with_creds is a execute tool on the MCP Framework Personal MCP server. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_with_creds? +

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

What risk level is run_with_creds? +

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

Can I rate-limit run_with_creds? +

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

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

run_with_creds is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 912 MCP Framework Personal tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →extract_with_root on Android Forensics ADB MCP Server →shortcuts_run on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →