Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion.
AI agents call check_import_status to retrieve information from Lara without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves the status and progress of an existing import job. It does not modify, create, delete, execute code, or trigger financial transactions. It is purely informational polling with no side effects on the system state.
From the tool's definition Tool description states 'Checks the status of a TMX import job' and 'Poll this tool' to track progress. The verb 'checks' and the nature of polling a status field indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion. It is categorised as a Read tool in the Lara MCP Server, which means it retrieves data without modifying state.
Register the Lara MCP server in PolicyLayer and add a rule for check_import_status: 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 Lara. Nothing to install.
check_import_status 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 check_import_status 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 check_import_status. 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.
check_import_status is provided by the Lara MCP server (@translated/lara-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 →