AI agents call get_mock_call_logs 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 and queries existing mock call log data without creating, modifying, deleting, or executing operations. It has no side effects and falls clearly into the Read category. Severity is low because mock call logs are typically non-sensitive metadata with no blast radius if accessed inappropriately.
From the tool's definition Tool name and description indicate retrieval of mock call logs: 'Get mock call logs' with no modification, deletion, or execution semantics. Returns historical log data with size/count limits ('Maximum 6.5MB or 100 call logs per API call').
Attacks that exploit this kind of access
Get mock call logs. Maximum 6.5MB or 100 call logs per API call. Retention period based on Postman plan. 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_call_logs: 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_call_logs 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_call_logs 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_call_logs. 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_call_logs 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 →