unpublish_mock
Unpublish mock server (sets Access Control to private)
This record as markdown: /tools/delano-postman-mcp-server/unpublish-mock.md
What unpublish_mock does on Postman
AI agents use unpublish_mock to create or update resources in Postman, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Postman environment.
Why unpublish_mock is rated Medium
This tool changes the visibility/access control of a mock server from public to private. This is a reversible write operation (it can be published again), not a deletion or destruction of data. The blast radius is medium as it could affect integrations or users relying on the public mock server endpoint.
From the tool's definition Unpublish mock server (sets Access Control to private)
Attacks that exploit this kind of access
The rule that runs unpublish_mock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unpublish_mock, this is the rule to start with:
unpublish_mock stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every unpublish_mock call is checked against it from then on.
Questions about unpublish_mock
Unpublish mock server (sets Access Control to private). It is categorised as a Write tool in the Postman MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Postman MCP server in PolicyLayer and add a rule for unpublish_mock: 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 Postman. Nothing to install.
unpublish_mock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unpublish_mock 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.
Set action: deny in the PolicyLayer policy for unpublish_mock. 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.
unpublish_mock is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue