Get a single work order by ID, including tenant, unit, and attachments.
AI agents call get_work_order to retrieve information from Lanten 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 existing work order data by ID and returns associated information (tenant, unit, attachments). It performs no mutations, deletions, or external operations. The blast radius of misuse is minimal—an agent could only access existing work order records it has authorization to view, with no ability to modify or delete data.
From the tool's definition Tool name 'get_work_order' and description 'Get a single work order by ID' indicate a retrieval operation with no side effects. The verb 'Get' and absence of modification language confirm this is a read-only query.
Attacks that exploit this kind of access
Get a single work order by ID, including tenant, unit, and attachments. It is categorised as a Read tool in the Lanten MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lanten MCP Server MCP server in PolicyLayer and add a rule for get_work_order: 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 Lanten MCP Server. Nothing to install.
get_work_order 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_work_order 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_work_order. 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_work_order is provided by the Lanten MCP Server MCP server (lanten-ai/mcp-server). 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 →