get-endpoint
AI agents call get-endpoint to retrieve information from RunPod MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get-endpoint' tool retrieves endpoint configuration or status information from RunPod without modifying, deleting, or executing operations. Though the description is empty, the naming convention and context of a resource management API clearly indicate this is a Read operation. The blast radius of misuse is limited to information disclosure, warranting low severity.
From the tool's definition Tool name 'get-endpoint' indicates a retrieval operation. Server description confirms this MCP server manages RunPod resources including 'endpoints', and the 'get-' prefix is a standard convention for read-only data retrieval without side effects.
Attacks that exploit this kind of access
get-endpoint. It is categorised as a Read tool in the RunPod MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunPod MCP Server MCP server in PolicyLayer and add a rule for get-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.
get-endpoint is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-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 get-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.
get-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 →