AI agents call check_glossary_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 purely queries the state of an existing import process and returns status information. It has no side effects, does not modify data, does not execute operations, and does not perform destructive or financial actions. It is a straightforward status-checking utility, which falls squarely into the Read category.
From the tool's definition The tool description states it 'Checks the status of a glossary CSV import job' and instructs to 'Poll this tool with the import_id'.
Attacks that exploit this kind of access
Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_id returned from import_glossary_csv until the import is complete. 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_glossary_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_glossary_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_glossary_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_glossary_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_glossary_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 →