Retrieve a single technical user by its UUID.
AI agents call get_technical_user 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 performs a simple retrieval operation on a single technical user record using a UUID identifier. It queries existing data without creating, modifying, deleting, or executing operations. The read-only nature of the server and the retrieval-focused language ('Retrieve') confirm this is a Read category tool.
From the tool's definition Tool name 'get_technical_user' and description 'Retrieve a single technical user by its UUID' indicate a query operation that retrieves data without modification. The server description confirms 'read-only access' to the LeanIX MTM API.
Attacks that exploit this kind of access
Retrieve a single technical user by its UUID. 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_technical_user: 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_technical_user 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_technical_user 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_technical_user. 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_technical_user 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 →