Low Risk

get_api_surface

Pull the complete structured API surface for a single developer API vendor — every HTTP endpoint (method + path + summary + params + returns), every documented SDK method, the authentication scheme, the detected languages, and the docs root URL. Takes a vendor

How to control get_api_surface ↓

AI agents call get_api_surface to retrieve information from Nextdev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and queries structured metadata about API surfaces (endpoints, documentation, schemas, authentication details) with no side effects. It is purely informational—it does not execute any of the APIs it describes, create resources, modify data, or trigger external operations.

From the tool's definition Tool description states it 'Pull[s] the complete structured API surface' and lists endpoints, methods, parameters, returns, authentication scheme, languages, and documentation root URL.

Risk signalsAdmin/system-level operation

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_api_surface": {}
  }
}

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

  1. Create a free account and register Nextdev MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_api_surface tool do? +

Pull the complete structured API surface for a single developer API vendor — every HTTP endpoint (method + path + summary + params + returns), every documented SDK method, the authentication scheme, the detected languages, and the docs root URL. Takes a vendor. It is categorised as a Read tool in the Nextdev MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_api_surface? +

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

What risk level is get_api_surface? +

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

Can I rate-limit get_api_surface? +

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

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

get_api_surface is provided by the Nextdev MCP server (nextdev-labs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nextdev MCP tool call.

Deterministic rules across all 7 Nextdev MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

7 Nextdev MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.