List your XERT activities within a specified time range.
AI agents call xert-list-activities to retrieve information from XERT Cycling Training without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays a list of cycling activities filtered by date range. It has no side effects, does not modify data, execute commands, delete records, or involve financial transactions. It is a straightforward read-only query operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool name 'xert-list-activities' and description 'List your XERT activities within a specified time range' indicate data retrieval with no modification or execution. The verb 'list' is a query operation that returns existing data.
Attacks that exploit this kind of access
List your XERT activities within a specified time range. It is categorised as a Read tool in the XERT Cycling Training MCP Server, which means it retrieves data without modifying state.
Register the XERT Cycling Training MCP server in PolicyLayer and add a rule for xert-list-activities: 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 XERT Cycling Training. Nothing to install.
xert-list-activities 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 xert-list-activities 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 xert-list-activities. 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.
xert-list-activities is provided by the XERT Cycling Training MCP server (milofax/xert-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 →