get_pull_request_metrics

THE RISK

Low Risk

Why get_pull_request_metrics needs a policy

This tool retrieves engineering metrics from Swarmia's API without modifying, executing, or deleting any data. It is purely informational and presents no risk of unintended side effects even if called repeatedly or with unexpected arguments. The blast radius of misuse is minimal—worst case, an agent queries metrics unnecessarily, consuming API quota but causing no damage.

From the tool's definition Tool name 'get_pull_request_metrics' and description 'Get pull request metrics' indicate data retrieval. The description specifies read-only metrics querying (cycle time, review rate, merge time) with no modification, deletion, or execution capabilities.

Documented attack patterns abuse exactly the kind of access get_pull_request_metrics gives an agent:

POLICY

How to control get_pull_request_metrics

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_pull_request_metrics:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_pull_request_metrics": {}
  }
}

get_pull_request_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Swarmia MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Swarmia MCP Server tools

Read get_dora_metrics Get DORA metrics including deployment frequency, change lead time, change failure rate, et Read get_effort_reporting Get effort reporting showing authors and their FTE for each issue in a given month Read get_investment_balance Get investment balance statistics using the Effort model (monthly FTE data) Read get_software_capitalization_employees Get list of employees with FTE effort breakdown for each month of the year Read get_software_capitalization_report Get software capitalization report with employee contributions to capitalizable work

All 6 Swarmia MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_pull_request_metrics

What does the get_pull_request_metrics tool do? +

Get pull request metrics for the organization including cycle time, review rate, merge time, etc. It is categorised as a Read tool in the Swarmia MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pull_request_metrics? +

Register the Swarmia MCP Server MCP server in PolicyLayer and add a rule for get_pull_request_metrics: 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.

What risk level is get_pull_request_metrics? +

get_pull_request_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pull_request_metrics? +

Yes. Add a rate_limit block to the get_pull_request_metrics 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.

How do I block get_pull_request_metrics completely? +

Set action: deny in the PolicyLayer policy for get_pull_request_metrics. 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.

What MCP server provides get_pull_request_metrics? +

get_pull_request_metrics 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.

Enforce policy on every Swarmia MCP Server tool call.

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.

CHECK YOUR STACK →