coding_overseer

Ask the cross-repo Overseer agent. It sees all repos, their live sessions, and recent terminal output. Can answer questions and drive Claude Code on specific repos.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/coding-overseer.md

WHAT IT DOES

What coding_overseer does on ProAgentStore

AI agents invoke coding_overseer to trigger actions in ProAgentStore. 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 coding_overseer is rated High

This tool goes beyond read access: it can 'drive Claude Code on specific repos', meaning it can trigger code execution, terminal commands, and modifications across repositories. The cross-repo scope and live session access amplify the blast radius significantly. It is classified as Execute because it can initiate actions in external environments, not merely read data.

From the tool's definition 'drive Claude Code on specific repos' and 'sees all repos, their live sessions, and recent terminal output' — the tool can actively trigger code execution across multiple repositories via an overseer agent

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs coding_overseer safely

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

coding_overseer Rate-limited

coding_overseer 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": {
    "coding_overseer": {
      "limits": [
        {
          "counter": "coding_overseer_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 ProAgentStore, apply this rule, and every coding_overseer call is checked against it from then on.

FAQ

Questions about coding_overseer

What does the coding_overseer tool do? +

Ask the cross-repo Overseer agent. It sees all repos, their live sessions, and recent terminal output. Can answer questions and drive Claude Code on specific repos. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on coding_overseer? +

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

What risk level is coding_overseer? +

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

Can I rate-limit coding_overseer? +

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

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

coding_overseer is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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