Get effort reporting showing authors and their FTE for each issue in a given month
AI agents call get_effort_reporting to retrieve information from Swarmia MCP Server 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 engineering metrics (FTE data and effort allocation per author/issue) from the Swarmia Export API without modifying, deleting, or executing operations. It is a pure data query with no side effects. The blast radius of misuse is minimal—an agent could only retrieve engineering visibility data it may not be authorized to see, not cause operational harm.
From the tool's definition Tool name 'get_effort_reporting' and description 'Get effort reporting showing authors and their FTE for each issue in a given month' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access get_effort_reporting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swarmia MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_effort_reporting:
{
"version": "1",
"default": "deny",
"tools": {
"get_effort_reporting": {}
}
}get_effort_reporting 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.
Get effort reporting showing authors and their FTE for each issue in a given month. It is categorised as a Read tool in the Swarmia MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Swarmia MCP Server MCP server in PolicyLayer and add a rule for get_effort_reporting: 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 Swarmia MCP Server. Nothing to install.
get_effort_reporting 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_effort_reporting 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_effort_reporting. 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_effort_reporting is provided by the Swarmia MCP Server MCP server (mattjegan/swarmia-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Swarmia MCP Server, 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.
6 Swarmia MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.