get_mock_call_logs
Get mock call logs. Maximum 6.5MB or 100 call logs per API call. Retention period based on Postman plan.
This record as markdown: /tools/delano-postman-mcp-server/get-mock-call-logs.md
What get_mock_call_logs does on Postman
AI agents call get_mock_call_logs to retrieve information from Postman without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_mock_call_logs is rated Low
This tool retrieves historical log data from Postman's mock server infrastructure. The 'get' verb combined with 'logs' (read-only audit/diagnostic data) confirms it is a Read operation. The severity is low because logs typically contain operational metadata without direct access to sensitive API keys or production data, though logs may contain request/response details depending on what Postman stores.
From the tool's definition Tool name 'get_mock_call_logs' and description 'Get mock call logs' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_mock_call_logs 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 get_mock_call_logs, this is the rule to start with:
get_mock_call_logs is read-only, so it stays allowed. 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 get_mock_call_logs call is checked against it from then on.
Questions about get_mock_call_logs
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 (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