log_command_tool · Mcp Commands MCP: Risk & Policy

WHAT IT DOES

What log_command_tool does on Mcp Commands

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

WHY IT NEEDS A POLICY

Why log_command_tool needs a policy

This tool writes a new log entry to the PostgreSQL database recording an AI command usage. It is a straightforward write/create operation with no destructive, executable, or financial implications. Misuse risk is low since it only adds tracking records.

From the tool's definition 'Log one AI command usage' — creates a new record in the database tracking command history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_command_tool Rate-limited

log_command_tool 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_command_tool": {
      "limits": [
        {
          "counter": "log_command_tool_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 Commands, so you can run agents against it safely.

FAQ

Questions about log_command_tool

What does the log_command_tool tool do? +

Log one AI command usage. It is categorised as a Write tool in the Mcp Commands 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_command_tool? +

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

What risk level is log_command_tool? +

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

Can I rate-limit log_command_tool? +

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

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

log_command_tool is provided by the Mcp Commands MCP server (puemmth/mcp-commands). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.