get_endpoint_details

THE RISK

Low Risk

Why get_endpoint_details needs a policy

This tool retrieves API documentation or endpoint metadata. It is a read-only operation with no side effects—it does not control robot hardware, create/modify runs, execute commands, or delete data. The verb 'Get' and the context of retrieving endpoint details confirm this is informational retrieval. Low severity because misuse would only expose API documentation, not cause robot malfunction or data loss.

From the tool's definition Tool name 'get_endpoint_details' and description 'Get comprehensive details about a specific API endpoint' indicate a retrieval operation that queries endpoint information without modifying state or triggering robot actions.

Documented attack patterns abuse exactly the kind of access get_endpoint_details gives an agent:

POLICY

How to control get_endpoint_details

PolicyLayer is an MCP gateway — it sits between your AI agents and Opentrons MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_endpoint_details:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_endpoint_details": {}
  }
}

get_endpoint_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Opentrons MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Opentrons MCP Server tools

Execute control_run Control run execution (play, pause, stop, resume) Execute home_robot Home robot axes or specific pipette Execute poll_error_endpoint_and_fix Fetch specific JSON error report and automatically fix protocols Execute create_run Create a new protocol run on the robot Write control_lights Turn robot lights on or off Write upload_protocol Upload a protocol file to an Opentrons robot Read get_api_overview Get high-level overview of the Opentrons HTTP API structure and capabilities Read get_protocols List all protocols stored on the robot

All 14 Opentrons MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_endpoint_details

What does the get_endpoint_details tool do? +

Get comprehensive details about a specific API endpoint. It is categorised as a Read tool in the Opentrons MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_endpoint_details? +

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

What risk level is get_endpoint_details? +

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

Can I rate-limit get_endpoint_details? +

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

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

get_endpoint_details is provided by the Opentrons MCP Server MCP server (yerbymatey/opentrons-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Opentrons MCP Server tool call.

Start from Opentrons MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →