Retrieve configuration and metadata for a single monitoring task by ID.
AI agents call lenx_get_task to retrieve information from Lenx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries task information without side effects. It returns existing data about a monitoring task without creating, modifying, or deleting anything. The low severity reflects the limited blast radius of misuse—an agent could retrieve unintended task metadata, but cannot cause irreversible changes or execute external actions.
From the tool's definition Tool retrieves 'configuration and metadata for a single monitoring task by ID' with no indication of data modification, deletion, or execution capability.
Attacks that exploit this kind of access
Retrieve configuration and metadata for a single monitoring task by ID. It is categorised as a Read tool in the Lenx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lenx MCP Server MCP server in PolicyLayer and add a rule for lenx_get_task: 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 Lenx MCP Server. Nothing to install.
lenx_get_task 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 lenx_get_task 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 lenx_get_task. 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.
lenx_get_task is provided by the Lenx MCP Server MCP server (thinkcol/lenx-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 →