procore_api_call · Procore MCP Server MCP: Risk & Policy

WHAT IT DOES

What procore_api_call does on Procore MCP Server

AI agents invoke procore_api_call to trigger actions in Procore MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why procore_api_call needs a policy

This is an Execute-category tool because it runs external operations (REST API calls) whose effects depend entirely on what arguments are passed to it. While it could theoretically be used for reads, writes, destructive actions, or financial operations depending on which endpoint is called, the tool itself is a generic executor.

From the tool's definition Tool is described as 'Execute any Procore REST API call' and explicitly called 'the workhorse' for making API calls.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

procore_api_call Rate-limited

procore_api_call stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "procore_api_call": {
      "limits": [
        {
          "counter": "procore_api_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Procore MCP Server, so you can run agents against it safely.

FAQ

Questions about procore_api_call

What does the procore_api_call tool do? +

Execute any Procore REST API call. This is the workhorse — first use the. It is categorised as a Execute tool in the Procore MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on procore_api_call? +

Register the Procore MCP Server MCP server in PolicyLayer and add a rule for procore_api_call: 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 Procore MCP Server. Nothing to install.

What risk level is procore_api_call? +

procore_api_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit procore_api_call? +

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

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

procore_api_call is provided by the Procore MCP Server MCP server (tylerilunga/procore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.