get_endpoint_status

Get status and health of a model endpoint

SERVERClaude MCP Server Ecosystem SOURCEcoder-rl/claude_mcpserver_dev1
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/get-endpoint-status.md

What get_endpoint_status does on Claude MCP Server Ecosystem

AI agents call get_endpoint_status to retrieve information from Claude MCP Server Ecosystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_endpoint_status is rated Low

This tool performs a read-only query to fetch the status and health metrics of a model endpoint. It retrieves data without side effects, altering state, executing code, or triggering irreversible changes. The verb 'get' combined with 'status' and 'health' clearly indicates a retrieval operation typical of monitoring or observability infrastructure.

From the tool's definition Tool name 'get_endpoint_status' and description 'Get status and health of a model endpoint' indicate a query operation that retrieves status information without modifying or triggering external operations.

Questions about get_endpoint_status

What does the get_endpoint_status tool do? +

Get status and health of a model endpoint. It is categorised as a Read tool in the Claude MCP Server Ecosystem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_endpoint_status? +

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

What risk level is get_endpoint_status? +

get_endpoint_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_endpoint_status? +

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

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

get_endpoint_status is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Claude MCP Server Ecosystem, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude MCP Server Ecosystem's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.