run_write

A write tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/run-write.md

WHAT IT DOES

What run_write does on Mcpg

AI agents use run_write to create or update resources in Mcpg, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcpg environment.

RISK

Why run_write is rated Medium

The name 'run_write' strongly suggests it executes write operations against the PostgreSQL database. On a production-grade PostgreSQL MCP server, a write tool could create or modify data. However, since the description is empty, there is uncertainty about whether it could also execute arbitrary SQL (including destructive statements).

From the tool's definition Tool name 'run_write' implies write operations; description is empty providing no further clarification

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_write safely

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

run_write Rate-limited

run_write 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": {
    "run_write": {
      "limits": [
        {
          "counter": "run_write_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about run_write

What does the run_write tool do? +

run_write is a write tool on the Mcpg MCP server. It is categorised as a Write tool in the Mcpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on run_write? +

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

What risk level is run_write? +

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

Can I rate-limit run_write? +

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

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

run_write is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

team_manager_write_memory on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →