Performance of users completing the most tasks. Count the number of completed tasks by user for the provided period. By default the user with the most completed tasks is shown first.
AI agents call getProjectsPeopleMetricsPerformance to retrieve information from Teamwork MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing task completion data to generate performance metrics. It performs no write, delete, or execute operations—it merely aggregates and returns information about completed tasks by user for analysis purposes. This is a classic Read operation with minimal risk.
From the tool's definition The tool description states it counts and shows performance metrics ('performance of users', 'number of completed tasks by user'). The verb 'count' and 'show' indicate data retrieval with no modification. No side effects are described.
Documented attack patterns abuse exactly the kind of access getProjectsPeopleMetricsPerformance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teamwork MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for getProjectsPeopleMetricsPerformance:
{
"version": "1",
"default": "deny",
"tools": {
"getProjectsPeopleMetricsPerformance": {}
}
}getProjectsPeopleMetricsPerformance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Performance of users completing the most tasks. Count the number of completed tasks by user for the provided period. By default the user with the most completed tasks is shown first. It is categorised as a Read tool in the Teamwork MCP MCP Server, which means it retrieves data without modifying state.
Register the Teamwork MCP server in PolicyLayer and add a rule for getProjectsPeopleMetricsPerformance: 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 Teamwork MCP. Nothing to install.
getProjectsPeopleMetricsPerformance 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 getProjectsPeopleMetricsPerformance 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 getProjectsPeopleMetricsPerformance. 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.
getProjectsPeopleMetricsPerformance is provided by the Teamwork MCP server (vizioz/teamwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teamwork MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Teamwork MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.