get_workspace_roles
Get roles for a specific workspace
This record as markdown: /tools/delano-postman-mcp-server/get-workspace-roles.md
What get_workspace_roles does on Postman
AI agents call get_workspace_roles 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_workspace_roles is rated Low
This tool queries and retrieves workspace role information, which is a read-only operation. It retrieves existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is low—an attacker could learn about organizational structure but cannot alter systems or access restricted data without additional compromised credentials.
From the tool's definition Tool name 'get_workspace_roles' and description 'Get roles for a specific workspace' both indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs get_workspace_roles 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_workspace_roles, this is the rule to start with:
get_workspace_roles 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_workspace_roles call is checked against it from then on.
Questions about get_workspace_roles
Get roles for a specific workspace. 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_workspace_roles: 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_workspace_roles 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_workspace_roles 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_workspace_roles. 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_workspace_roles 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