// MCP TOOL REFERENCE

APIDECK MCP SERVER TOOLS

4 tools from the Apideck MCP Server MCP Server, categorised by risk level.

READ TOOLS

describe_tool_input Get the input schema for one or more tools. It is a good idea to call this tool first to understand how to successfully call execute_tool. list_scopes List the scopes available on this server. Scopes are categories that group related tools together. They can be used as search terms when filtering ... list_tools List available tools. Optionally filter by search terms that match against tool name, description, and scopes.

EXECUTE TOOLS

execute_tool Execute a tool by name with the provided input parameters. If executing a given tool for the first time, it is recommended to call describe_tool_in... 3/5

// FAQ

How many tools does the Apideck MCP Server MCP server have? +

The Apideck MCP Server MCP server exposes 4 tools across 2 categories: Read, Execute.

How do I enforce policies on Apideck MCP Server tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Apideck MCP Server server.

What risk categories do Apideck MCP Server tools fall into? +

Apideck MCP Server tools are categorised as Read (3), Execute (1). Each category has a recommended default policy.

Enforce policies on Apideck MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →