AI agents use create_api_comment 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.
This tool creates a new comment, which is a reversible write operation. Comments can typically be edited or deleted, and creating a comment does not irreversibly destroy data, execute arbitrary code, or move money. The blast radius of misuse is minimal—an unwanted comment is a nuisance but easily remediated. Severity is low because the operation is non-destructive and non-disruptive to system functionality.
From the tool's definition Tool name is 'create_api_comment' and description states 'Create a new comment on an API'. The verb 'create' and action of adding a comment indicates data modification, not retrieval or deletion.
Attacks that exploit this kind of access
Create a new comment on an API (max 10,000 characters). 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 create_api_comment: 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.
create_api_comment 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 create_api_comment 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 create_api_comment. 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.
create_api_comment 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 →