30 tools from the Postman MCP Server, categorised by risk level.
View the Postman policy →getApi Get API details from Postman 2/5 getCollection Retrieve collection details 2/5 getEnvironment Get environment details 2/5 getMock Get mock server details 2/5 getMonitor Get monitor details 2/5 getWorkspace Get information about a specific workspace 2/5 listApis List APIs in a workspace 2/5 listCollections List collections in a workspace 2/5 listEnvironments List environments in a workspace 2/5 listMocks List mock servers 2/5 listMonitors List monitors 2/5 listWorkspaces List all Postman workspaces 2/5 createApi Create a new API in Postman 3/5 createCollection Create a new request collection 3/5 createEnvironment Create a new environment 3/5 createMock Create a mock server 3/5 createMonitor Create a monitor for a collection 4/5 createWorkspace Create a new Postman workspace 3/5 updateApi Update an API definition 3/5 updateCollection Update a request collection 3/5 updateEnvironment Update environment variables 4/5 updateMock Update a mock server configuration 3/5 updateWorkspace Update a workspace 3/5 The Postman MCP server exposes 30 tools across 4 categories: Read, Write, Destructive, Execute.
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 Postman server.
Postman tools are categorised as Read (12), Write (11), Destructive (6), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept