sys_process · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What sys_process does on RedisNexus

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

WHY IT NEEDS A POLICY

Why sys_process needs a policy

An AI agent can call sys_process faster than any human can review — one bad instruction and it creates or modifies resources in RedisNexus by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sys_process Rate-limited

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

FAQ

Questions about sys_process

What does the sys_process tool do? +

Manage processes: list top consumers, find by name, kill by PID. It is categorised as a Write tool in the RedisNexus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sys_process? +

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

What risk level is sys_process? +

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

Can I rate-limit sys_process? +

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

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

sys_process is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.