call_tool_logger_manager · Superkit MCP: Risk & Policy

WHAT IT DOES

What call_tool_logger_manager does on Superkit

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

PARAMETERS

Parameter	Type	Required
`name`	string	—
`action`	string	Yes
`outcome`	string	—
`projectPath`	string	Yes

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why call_tool_logger_manager needs a policy

The tool manages logging operations including log rotation, which involves writing log data and potentially overwriting/rotating log files. 'Manages' implies active modification of logging state. Log rotation could overwrite or truncate old logs, but this is a standard reversible write/administrative operation rather than a fully destructive one.

From the tool's definition 'Manages tool logging operations (skills, workflows, log rotation)'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

call_tool_logger_manager Rate-limited

call_tool_logger_manager 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": {
    "call_tool_logger_manager": {
      "limits": [
        {
          "counter": "call_tool_logger_manager_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 Superkit, so you can run agents against it safely.

FAQ

Questions about call_tool_logger_manager

What does the call_tool_logger_manager tool do? +

Manages tool logging operations (skills, workflows, log rotation). It is categorised as a Write tool in the Superkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does call_tool_logger_manager accept? +

call_tool_logger_manager accepts 4 parameters: name, action, outcome, projectPath. Required: action, projectPath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on call_tool_logger_manager? +

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

What risk level is call_tool_logger_manager? +

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

Can I rate-limit call_tool_logger_manager? +

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

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

call_tool_logger_manager is provided by the Superkit MCP server (superkit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.