AI agents call health_check 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 queries system state and connectivity information without creating, modifying, deleting, or executing external operations. It is purely diagnostic/observational in nature, making it a Read operation with low severity since it poses minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Perform[s] a local system health check' and 'Returns system information and configuration status.' The verb 'check' and 'returns' indicate data retrieval with no modifications. No side effects are described.
Attacks that exploit this kind of access
Perform a local system health check to verify Postman MCP server configuration and connectivity. Returns system information and configuration status. 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 health_check: 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.
health_check 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 health_check 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 health_check. 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.
health_check 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 →