List all workspaces for the requesting user with filtering and pagination support.
AI agents call get_workspaces to retrieve information from LeanIX MTM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists workspace data with no side effects. It is a read-only query operation that returns information to the user without modifying, deleting, or executing any operations. The low severity reflects minimal blast radius—unauthorized access to workspace listings could expose organizational structure but does not enable destructive or financial actions.
From the tool's definition Tool name 'get_workspaces' and description 'List all workspaces' indicates a query/retrieval operation. Server description explicitly states 'read-only access' to API data.
Attacks that exploit this kind of access
List all workspaces for the requesting user with filtering and pagination support. It is categorised as a Read tool in the LeanIX MTM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LeanIX MTM MCP Server MCP server in PolicyLayer and add a rule for get_workspaces: 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 LeanIX MTM MCP Server. Nothing to install.
get_workspaces 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_workspaces 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_workspaces. 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_workspaces is provided by the LeanIX MTM MCP Server MCP server (tomgutt/leanix-mtm-mcp). 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 →