// SCAN REPORT

MCP Coding Agents

7 tools. 4 can modify or destroy data without limits.

4 write tools that can modify data. Rate limits recommended.

Last updated: 1 Jul 2026

4 can modify or destroy data

3 read-only

7 tools total

Community server · catalogue entry verified 01/07/2026

How to control MCP Coding Agents ↓

TOOL MAP

What MCP Coding Agents exposes to your agents

Read (3) Write / Execute (4) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Coding Agents tools

Execute · Critical execute_command This tool can run arbitrary shell commands, making it Execute category rather than lower-risk categories. Execute · High claude_code_query This tool executes Claude Code queries, which can run arbitrary code or shell commands through the Claude Code agent. Execute · High codex_query This tool runs queries through the Codex CLI, which is an AI coding agent capable of generating and executing code, shell commands, and file modifications. Execute · High gemini_query The tool executes queries via the Gemini CLI, which is an AI coding agent capable of running commands, generating and executing code, and interacting with the filesystem.

4 of MCP Coding Agents's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Coding Agents

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Coding Agents, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "calculate_bmi": {
    "limits": [
      {
        "counter": "calculate_bmi_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Coding Agents — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP CODING AGENTS →

Instant setup, no code required.

FULL CATALOGUE

All 7 MCP Coding Agents tools

EXECUTE 4 tools

Execute claude_code_query Execute a Claude Code query with real-time message streaming Execute codex_query Execute a query using the Codex CLI tool with real-time streaming Execute execute_command Execute a shell command synchronously and return its output Execute gemini_query Execute a query using the Gemini CLI tool

READ 3 tools

Read calculate_bmi Calculate Body Mass Index (BMI) Read get_timestamp Get the current timestamp Read stream_sse_timestamps Generate 10 timestamps stremaing

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MCP Coding Agents

Is the MCP Coding Agents MCP server safe to use without restrictions? +

The MCP Coding Agents server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the MCP Coding Agents MCP server expose? +

7 tools across 2 categories: Execute, Read. 3 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on MCP Coding Agents? +

Register the MCP Coding Agents MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Coding Agents tool call.

Deterministic rules across all 7 MCP Coding Agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP CODING AGENTS →

Instant setup, no code required.

7 MCP Coding Agents tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from MCP Coding Agents's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →