create_api_endpoint · MCP Software Engineer MCP

WHAT IT DOES

What create_api_endpoint does on MCP Software Engineer

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

WHY IT NEEDS A POLICY

Why create_api_endpoint needs a policy

This tool creates and modifies API endpoints and associated operations. While 'Create' suggests Write category, CRUD operations include Create, Read, Update, Delete. The tool does not itself delete data (that would be Destructive), nor does it execute arbitrary code (that would be Execute). It creates/modifies API infrastructure and handlers, which is reversible via version control (commit_changes is available).

From the tool's definition Tool name is 'create_api_endpoint' and description states 'Create RESTful API endpoint with CRUD operations' – the verb 'Create' and 'CRUD operations' indicate data creation and modification capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_api_endpoint Rate-limited

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Software Engineer, so you can run agents against it safely.

FAQ

Questions about create_api_endpoint

What does the create_api_endpoint tool do? +

Create RESTful API endpoint with CRUD operations. It is categorised as a Write tool in the MCP Software Engineer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_api_endpoint? +

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

What risk level is create_api_endpoint? +

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

Can I rate-limit create_api_endpoint? +

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

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

create_api_endpoint is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.