AI agents call get_team_workload_report to retrieve information from Jamot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workload statistics (active task counts) for team members. It performs no data modification, deletion, or external execution—it is a pure query/reporting function. The blast radius of misuse is minimal: an AI agent could over-report or request excessive queries, but cannot harm data integrity or trigger side effects. Therefore, it falls squarely into the Read category with low severity.
From the tool's definition Tool name 'get_team_workload_report' and description 'Get active task count per user' indicate a read-only query operation that retrieves and aggregates task metrics without modifying any data.
Attacks that exploit this kind of access
Get active task count per user. It is categorised as a Read tool in the Jamot MCP MCP Server, which means it retrieves data without modifying state.
Register the Jamot MCP server in PolicyLayer and add a rule for get_team_workload_report: 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 Jamot MCP. Nothing to install.
get_team_workload_report 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_team_workload_report 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_team_workload_report. 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_team_workload_report is provided by the Jamot MCP server (jamot-pro/jamot-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 →