score_workflow · Sentinel Signal MCP: Risk & Policy

WHAT IT DOES

What score_workflow does on Sentinel Signal MCP

AI agents invoke score_workflow to trigger actions in Sentinel Signal MCP. 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 score_workflow needs a policy

This tool executes an external API call (POST) to score healthcare claims workflows including denial risk, prior authorization, and reimbursement assessment. While it appears to be read-like in intent (producing a score), it triggers external computation and side effects on a remote system, qualifying as Execute.

From the tool's definition 'unified workflow scoring (POST /v1/score)' — triggers an external POST operation that runs scoring logic against healthcare claims workflows

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

score_workflow Rate-limited

score_workflow 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": {
    "score_workflow": {
      "limits": [
        {
          "counter": "score_workflow_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 Sentinel Signal MCP, so you can run agents against it safely.

FAQ

Questions about score_workflow

What does the score_workflow tool do? +

Call Sentinel Signal unified workflow scoring (POST /v1/score). It is categorised as a Execute tool in the Sentinel Signal MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on score_workflow? +

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

What risk level is score_workflow? +

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

Can I rate-limit score_workflow? +

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

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

score_workflow is provided by the Sentinel Signal MCP server (sentinelsignal/sentinel-signal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.