setup_logging · MCP Software Engineer MCP: Risk & Policy

WHAT IT DOES

What setup_logging does on MCP Software Engineer

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

WHY IT NEEDS A POLICY

Why setup_logging needs a policy

The tool modifies logging infrastructure by setting up or reconfiguring logging systems. While this creates/modifies system configuration (Write category), it does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). It is reversible by reconfiguring logging again.

From the tool's definition Tool name 'setup_logging' and description 'Setup logging system with different levels and outputs' indicate it creates or modifies logging configuration in a codebase. This is a configuration write operation that affects system behavior but is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_logging Rate-limited

setup_logging 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": {
    "setup_logging": {
      "limits": [
        {
          "counter": "setup_logging_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 Software Engineer, so you can run agents against it safely.

FAQ

Questions about setup_logging

What does the setup_logging tool do? +

Setup logging system with different levels and outputs. It is categorised as a Write tool in the MCP Software Engineer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on setup_logging? +

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

What risk level is setup_logging? +

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

Can I rate-limit setup_logging? +

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

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

setup_logging is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.