get_pipeline_metrics

THE RISK

Low Risk

Why get_pipeline_metrics needs a policy

This tool retrieves analytical data about job pipelines without creating, modifying, or deleting any records. It is a pure data retrieval operation with no side effects on the Applicant Tracking System state. The blast radius of misuse is minimal—an agent could only access metrics data that may already be visible through the ATS interface.

From the tool's definition Tool name 'get_pipeline_metrics' and description 'Get pipeline metrics for jobs' indicate a retrieval operation with no modification capability. The verb 'Get' and the metrics query pattern are characteristic of read-only operations.

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

POLICY

How to control get_pipeline_metrics

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ashby Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for get_pipeline_metrics:

policy.json

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

get_pipeline_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 MCP Ashby Connector — 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 MCP Ashby Connector tools

Write bulk_create_candidates Create multiple candidates in a single operation Write bulk_schedule_interviews Schedule multiple interviews in a single operation Write bulk_update_applications Update multiple applications in a single operation Write create_application Creates a new application Write create_candidate Creates a new candidate in Ashby Write create_interview Creates a new interview Write create_job Creates a new job posting Read list_applications List applications with pagination and filtering

All 13 MCP Ashby Connector 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_pipeline_metrics

What does the get_pipeline_metrics tool do? +

Get pipeline metrics for jobs. It is categorised as a Read tool in the MCP Ashby Connector MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pipeline_metrics? +

Register the MCP Ashby Connector MCP server in PolicyLayer and add a rule for get_pipeline_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 MCP Ashby Connector. Nothing to install.

What risk level is get_pipeline_metrics? +

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

Can I rate-limit get_pipeline_metrics? +

Yes. Add a rate_limit block to the get_pipeline_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_pipeline_metrics completely? +

Set action: deny in the PolicyLayer policy for get_pipeline_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_pipeline_metrics? +

get_pipeline_metrics is provided by the MCP Ashby Connector MCP server (thnico/mcp-ashby). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Ashby Connector tool call.

Start from MCP Ashby Connector, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →