log_blocker | PolicyLayer

WHAT IT DOES

What log_blocker does on Studio Catharsis Universal Project Coordinator MCP

AI agents use log_blocker to create or update resources in Studio Catharsis Universal Project Coordinator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Studio Catharsis Universal Project Coordinator MCP environment.

WHY IT NEEDS A POLICY

Why log_blocker needs a policy

This tool creates or records blocker entries in the project coordination state, which is a reversible write operation. It does not read-only (no query/retrieval), does not execute arbitrary code, and does not delete or move money.

From the tool's definition The tool name 'log_blocker' and description 'Log a blocker that's preventing progress' indicate creation of new blocker records in a shared project state. The verb 'log' implies recording/writing new data to a persistent store (blocker tracking system).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_blocker Rate-limited

log_blocker stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_blocker": {
      "limits": [
        {
          "counter": "log_blocker_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Studio Catharsis Universal Project Coordinator MCP, so you can run agents against it safely.

FAQ

Questions about log_blocker

What does the log_blocker tool do? +

Log a blocker that's preventing progress. It is categorised as a Write tool in the Studio Catharsis Universal Project Coordinator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_blocker? +

Register the Studio Catharsis Universal Project Coordinator MCP server in PolicyLayer and add a rule for log_blocker: 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 Studio Catharsis Universal Project Coordinator MCP. Nothing to install.

What risk level is log_blocker? +

log_blocker is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_blocker? +

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

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

log_blocker is provided by the Studio Catharsis Universal Project Coordinator MCP server (studio-catharsis-creative-lab/project_com_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.