Low Risk

list_donut_syscalls

List the 14 NtFunctions used by the Donut shellcode loader project. Useful when generating stubs specifically for Donut-based payloads. Returns: Newline-separated list of Donut NtFunction names.

How to control list_donut_syscalls ↓

AI agents call list_donut_syscalls to retrieve information from Sysplant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool purely enumerates a static set of syscall function names used by the Donut project. It performs no code generation, execution, data modification, or destructive operations. While the context involves syscall code generation (which could enable malicious activity), this specific tool only reads and returns reference information.

From the tool's definition Tool 'list_donut_syscalls' returns a 'Newline-separated list of Donut NtFunction names' with no side effects. The verb 'list' and return-only behavior confirm retrieval without modification.

Documented attack patterns abuse exactly the kind of access list_donut_syscalls gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sysplant, and nothing reaches the server without passing your rules. This is the rule we recommend for list_donut_syscalls:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_donut_syscalls": {}
  }
}

list_donut_syscalls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sysplant — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the list_donut_syscalls tool do? +

List the 14 NtFunctions used by the Donut shellcode loader project. Useful when generating stubs specifically for Donut-based payloads. Returns: Newline-separated list of Donut NtFunction names. It is categorised as a Read tool in the Sysplant MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_donut_syscalls? +

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

What risk level is list_donut_syscalls? +

list_donut_syscalls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_donut_syscalls? +

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

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

list_donut_syscalls is provided by the Sysplant MCP server (x42en/sysplant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sysplant tool call.

Deterministic rules across all 9 Sysplant tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

9 Sysplant tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.