Re-run FRCP / state procedural deadline calculation for a matter. Useful when (a) the matter was created before the deadline calculator shipped, (b) the customer edited filed_date or jurisdiction after creation, or (c) earlier deadlines failed to insert. Idempotent — dedupes on lowercased title s...
Risk signalsHandles credentials or secrets (api_key)
Part of the Transaction Coordinator server.
Free to start. No card required.
AI agents invoke recompute_deadlines to trigger processes or run actions in Transaction Coordinator. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
recompute_deadlines can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"recompute_deadlines": {
"limits": [
{
"counter": "recompute_deadlines_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Transaction Coordinator policy for all 11 tools.
These attack patterns abuse exactly the kind of access recompute_deadlines gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Re-run FRCP / state procedural deadline calculation for a matter. Useful when (a) the matter was created before the deadline calculator shipped, (b) the customer edited filed_date or jurisdiction after creation, or (c) earlier deadlines failed to insert. Idempotent — dedupes on lowercased title so re-running can't duplicate. Args: matter_uuid: UUID of the matter to recompute. api_key: Your PrimaCoda MCP API key (starts 'pck_').. It is categorised as a Execute tool in the Transaction Coordinator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Transaction Coordinator MCP server in PolicyLayer and add a rule for recompute_deadlines: 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 Transaction Coordinator. Nothing to install.
recompute_deadlines is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the recompute_deadlines 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.
Set action: deny in the PolicyLayer policy for recompute_deadlines. 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.
recompute_deadlines is provided by the Transaction Coordinator MCP server (https://primacoda.halinc.tech/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Transaction Coordinator tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.