List all ~300+ supported NtFunction names. Returns every NtFunction that SysPlant knows how to generate a stub for, loaded from the built-in prototypes database. Returns: Newline-separated list of all NtFunction names (sorted).
AI agents call list_supported_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.
This tool only retrieves and queries data from a static database of syscall names. It performs no code generation, execution, modification, or deletion. It is purely informational—listing available syscalls that could be used by other tools like generate_syscalls, but the listing itself has no operational side effects. This is a classic Read operation (list, fetch).
From the tool's definition The tool 'list_supported_syscalls' returns a list of supported NtFunction names from a built-in database with no parameters for modification or execution.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list_supported_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_supported_syscalls:
{
"version": "1",
"default": "deny",
"tools": {
"list_supported_syscalls": {}
}
}list_supported_syscalls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all ~300+ supported NtFunction names. Returns every NtFunction that SysPlant knows how to generate a stub for, loaded from the built-in prototypes database. Returns: Newline-separated list of all NtFunction names (sorted). It is categorised as a Read tool in the Sysplant MCP Server, which means it retrieves data without modifying state.
Register the Sysplant MCP server in PolicyLayer and add a rule for list_supported_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.
list_supported_syscalls is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_supported_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.
Set action: deny in the PolicyLayer policy for list_supported_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.
list_supported_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.
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.