Retrieve all events for a specific workspace with pagination support.
AI agents call get_workspace_events 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 event data from a workspace without modifying, creating, or deleting any information. The 'get_' prefix and 'Retrieve' verb in the description confirm it is a simple data query with no destructive or mutative capabilities. Read-only access to event logs poses minimal risk.
From the tool's definition Tool name 'get_workspace_events' with description 'Retrieve all events for a specific workspace' indicates a read-only query operation. Server description explicitly states 'read-only access' and tool performs retrieval without side effects.
Attacks that exploit this kind of access
Retrieve all events for a specific workspace with 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_workspace_events: 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_workspace_events 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_events 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_events. 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_events 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 →