log_action_summary · Mcp Coordinator MCP: Risk & Policy

WHAT IT DOES

What log_action_summary does on Mcp Coordinator

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

WHY IT NEEDS A POLICY

Why log_action_summary needs a policy

This tool writes a log entry recording an action summary. It creates data (a log record) but does not delete, execute code, or involve finances. The blast radius is low since it only appends a summary string to a log.

From the tool's definition 'Log a one-liner summary of an action' — creates a log/audit record

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_action_summary Rate-limited

log_action_summary 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_action_summary": {
      "limits": [
        {
          "counter": "log_action_summary_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 Mcp Coordinator, so you can run agents against it safely.

FAQ

Questions about log_action_summary

What does the log_action_summary tool do? +

Log a one-liner summary of an action. It is categorised as a Write tool in the Mcp Coordinator 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_action_summary? +

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

What risk level is log_action_summary? +

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

Can I rate-limit log_action_summary? +

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

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

log_action_summary is provided by the Mcp Coordinator MCP server (swoofer/mcp-coordinator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.