list_endpoints

THE RISK

Low Risk

Why list_endpoints needs a policy

This tool queries and returns information about available endpoints without modifying, deleting, or executing any operations. It is a straightforward informational retrieval with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'list_endpoints' combined with description 'List available endpoints' indicates a retrieval operation with no side effects. The verb 'list' is explicitly a Read operation.

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

POLICY

How to control list_endpoints

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

policy.json

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

list_endpoints 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 TypeSpec 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 TypeSpec MCP Server tools

Destructive deleteTodo Delete a todo Destructive gists_delete Delete a gist Execute build Build typespec mcp project Execute compile Compile the typespec project in the given directory. Execute call_endpoint Call the given endpoint.\nUse the Execute math_dot_product Computes the dot product of two vectors. Use this to find the scalar\nprojection of one ve Execute math_sub_vector Subtracts one vector from another. Use this to find the difference between\ntwo vectors. F Execute math_add_vector Adds two vectors together. Use this when you want to combine two vectors to\nget a resulta

All 28 TypeSpec 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 list_endpoints

What does the list_endpoints tool do? +

List available endpoints. It is categorised as a Read tool in the TypeSpec MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_endpoints? +

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

What risk level is list_endpoints? +

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

Can I rate-limit list_endpoints? +

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

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

list_endpoints is provided by the TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TypeSpec MCP Server tool call.

Start from TypeSpec 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 →