AI agents use create_workspace 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 workspace resource in Postman, which is a reversible write operation. While it modifies the user's Postman environment by adding a new workspace, the action can be undone by deleting the workspace. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool name is 'create_workspace' and description states 'Create a new workspace', indicating it creates a new resource in Postman.
Documented attack patterns abuse exactly the kind of access create_workspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postman, and nothing reaches the server without passing your rules. This is the rule we recommend for create_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"create_workspace": {
"limits": [
{
"counter": "create_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_workspace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new workspace. 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_workspace: 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_workspace 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_workspace 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_workspace. 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_workspace is provided by the Postman MCP server (salehkhatri/postman-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Postman tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Postman tools catalogued and risk-classified — across an index of 42,500+ MCP servers.