quickbase_run_report · QuickBase MCP Server MCP

WHAT IT DOES

What quickbase_run_report does on QuickBase MCP Server

AI agents invoke quickbase_run_report to trigger actions in QuickBase 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 quickbase_run_report needs a policy

Running a report involves executing a server-side operation that may perform complex queries, aggregations, or trigger automated workflows in QuickBase. While it is primarily a read-like activity, 'run' implies execution of a defined process rather than a simple data fetch.

From the tool's definition 'Run a specific report' — executing/triggering a report operation rather than simply reading static data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quickbase_run_report Rate-limited

quickbase_run_report 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": {
    "quickbase_run_report": {
      "limits": [
        {
          "counter": "quickbase_run_report_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 QuickBase MCP Server, so you can run agents against it safely.

FAQ

Questions about quickbase_run_report

What does the quickbase_run_report tool do? +

Run a specific report. It is categorised as a Execute tool in the QuickBase 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 quickbase_run_report? +

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

What risk level is quickbase_run_report? +

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

Can I rate-limit quickbase_run_report? +

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

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

quickbase_run_report is provided by the QuickBase MCP Server MCP server (lawrencecirillo/quickbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.