publish_mock
Publish mock server (sets Access Control to public)
This record as markdown: /tools/delano-postman-mcp-server/publish-mock.md
What publish_mock does on Postman
AI agents use publish_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 publish_mock is rated Medium
Publishing a mock server changes its visibility/access control settings, which is a reversible modification. While this could increase exposure of API mocks, it is not destructive (the mock server itself is not deleted), not financial, not execute/code-running, and not a read operation.
From the tool's definition Tool description states 'Publish mock server (sets Access Control to public)' - this modifies the access control settings of an existing mock server from private to public.
Attacks that exploit this kind of access
The rule that runs publish_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 publish_mock, this is the rule to start with:
publish_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 publish_mock call is checked against it from then on.
Questions about publish_mock
Publish mock server (sets Access Control to public). 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 publish_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.
publish_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 publish_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 publish_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.
publish_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