create-endpoint
AI agents use create-endpoint to create or update resources in RunPod MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunPod MCP Server environment.
Creating an endpoint in RunPod instantiates a new inference endpoint, which is a resource that can serve models and incur compute costs. This is a reversible write operation (the endpoint can be deleted via delete-endpoint), not destructive. However, it has high severity because an AI agent creating arbitrary endpoints could lead to resource consumption, cost impact, and unauthorized service exposure.
From the tool's definition Tool name is 'create-endpoint' which indicates creation of a new endpoint resource in the RunPod system. Sibling tools like 'delete-endpoint' and other 'create-*' operations confirm this is a write operation that modifies RunPod infrastructure.
Attacks that exploit this kind of access
create-endpoint. It is categorised as a Write tool in the RunPod MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for create-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 RunPod MCP Server. Nothing to install.
create-endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-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.
Set action: deny in the PolicyLayer policy for create-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.
create-endpoint is provided by the RunPod MCP Server MCP server (niel-runpod/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →