AI agents call get_mock to retrieve information from Postman without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing mock server without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal risk if misused by an AI agent, as it only queries existing data.
From the tool's definition Tool name 'get_mock' and description 'Get details of a specific mock server' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific mock server. It is categorised as a Read tool in the Postman MCP Server, which means it retrieves data without modifying state.
Register the Postman MCP server in PolicyLayer and add a rule for get_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.
get_mock is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_mock is provided by the Postman MCP server (postmanv3/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →