Low Risk

rigor_workflows

List all Rigor workflows for your organization with filtering and pagination. Returns status, progress, capacity usage, and available actions per workflow. Use to monitor workflow state, understand concurrent limit usage, and identify stuck or completed workflows.

Part of the Plith server.

rigor_workflows is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PLITH →

Free to start. No card required.

AI agents call rigor_workflows to retrieve information from Plith without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though rigor_workflows only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "rigor_workflows": {}
  }
}

See the full Plith policy for all 15 tools.

Get this rule live on your own Plith server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PLITH →

View all 15 tools →

These attack patterns abuse exactly the kind of access rigor_workflows gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so rigor_workflows only ever does what you allow.

SECURE PLITH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the rigor_workflows tool do? +

List all Rigor workflows for your organization with filtering and pagination. Returns status, progress, capacity usage, and available actions per workflow. Use to monitor workflow state, understand concurrent limit usage, and identify stuck or completed workflows.. It is categorised as a Read tool in the Plith MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rigor_workflows? +

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

What risk level is rigor_workflows? +

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

Can I rate-limit rigor_workflows? +

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

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

rigor_workflows is provided by the Plith MCP server (https://plith.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Plith tool call.

Deterministic rules across all 15 Plith 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.