get_task_group_cycle_times
AI agents call get_task_group_cycle_times to retrieve information from PensionPro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context among sibling read-only tools (get_client_details, get_employee_stats, get_notes) strongly suggests this retrieves metrics without modification. No indication of write, execute, destructive, or financial operations. Low severity as this is data retrieval with no side effects.
From the tool's definition Tool name 'get_task_group_cycle_times' indicates retrieval of cycle time metrics for task groups; no description provided but naming convention aligns with sibling read tools (get_client_details, get_employee_stats, get_help_article, get_notes).
Attacks that exploit this kind of access
get_task_group_cycle_times. It is categorised as a Read tool in the PensionPro MCP Server, which means it retrieves data without modifying state.
Register the PensionPro MCP server in PolicyLayer and add a rule for get_task_group_cycle_times: 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 PensionPro. Nothing to install.
get_task_group_cycle_times 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 get_task_group_cycle_times 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 get_task_group_cycle_times. 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.
get_task_group_cycle_times is provided by the PensionPro MCP server (pypi:pension-pro-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 →