List monitoring tasks accessible to the authenticated user, with pagination support.
AI agents call lenx_list_tasks 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.
The tool retrieves and displays existing monitoring task data without creating, modifying, deleting, or executing operations. Pagination support confirms it is designed for safe data retrieval. The most severe sibling tool is lenx_delete_task (Destructive), but this tool itself performs only listing/querying.
From the tool's definition Tool name is 'lenx_list_tasks' and description states it 'List[s] monitoring tasks accessible to the authenticated user, with pagination support.' This is a read-only query operation with no side effects.
Attacks that exploit this kind of access
List monitoring tasks accessible to the authenticated user, with pagination support. 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_list_tasks: 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_list_tasks 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_list_tasks 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_list_tasks. 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_list_tasks 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 →