Add a syslog forwarding rule to send logs to an external syslog server.
AI agents use add_syslog_rule to create or update resources in Morpheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Morpheus MCP Server environment.
This tool creates or modifies logging configuration by adding a new syslog rule. While it changes system state, it is reversible (the rule can be removed or modified later) and does not delete data or execute arbitrary code. It falls into the Write category.
From the tool's definition Tool description states 'Add a syslog forwarding rule' which creates a new configuration entry. The verb 'Add' combined with 'forwarding rule' indicates a write operation that modifies system logging settings.
Attacks that exploit this kind of access
Add a syslog forwarding rule to send logs to an external syslog server. It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for add_syslog_rule: 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 Morpheus MCP Server. Nothing to install.
add_syslog_rule 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 add_syslog_rule 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 add_syslog_rule. 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.
add_syslog_rule is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →