log_management
Logging: auditd, journalctl, fail2ban, syslog, log rotation, SIEM integration
This record as markdown: /tools/defense/log-management.md
What log_management does on Defense
AI agents use log_management to create or update resources in Defense, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Defense environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
ip | string | — | IP address to ban or unban |
end | string | — | End time |
key | string | — | Audit key to search for |
uid | string | — | User ID to filter |
grep | string | — | Pattern to search for in log messages |
jail | string | — | Fail2ban jail name |
rule | string | — | Audit rule string |
unit | string | — | Systemd unit name to filter |
limit | number | — | Maximum lines to return |
lines | number | — | Number of log lines / max lines to return |
since | string | — | Start time, e.g. '1 hour ago', 'today' |
start | string | — | Start time, e.g. 'today', '1 hour ago' |
Parameters from the server's own tool schema.
Why log_management is rated Medium
An AI agent can call log_management faster than any human can review: one bad instruction and it creates or modifies resources in Defense by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (34 properties)
Attacks that exploit this kind of access
The rule that runs log_management safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Defense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For log_management, this is the rule to start with:
log_management 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Defense, apply this rule, and every log_management call is checked against it from then on.
Questions about log_management
Logging: auditd, journalctl, fail2ban, syslog, log rotation, SIEM integration. It is categorised as a Write tool in the Defense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
log_management accepts 12 parameters: ip, end, key, uid, grep, jail, rule, unit, limit, lines, since, start. The full parameter table on this page comes from the server's own tool schema.
Register the Defense MCP server in PolicyLayer and add a rule for log_management: 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 Defense. Nothing to install.
log_management is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_management 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.
Set action: deny in the PolicyLayer policy for log_management. 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.
log_management is provided by the Defense MCP server (defense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Defense, and thousands of servers like it.
This server
Across the catalogue