Scan source files for NtFunction / ZwFunction usage. Walks the given file or directory and detects which Nt/Zw functions are referenced. Useful for determining which syscalls your injection code needs. Supported file extensions: .h, .c, .cpp, .nim, .rs Args: search_path: Absolute path to a file o...
AI agents call scan_ntfunctions 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.
scan_ntfunctions performs static code analysis on source files to identify function usage patterns. It reads and searches files but does not modify, delete, execute, or write data. The operation is purely informational—extracting metadata about syscall dependencies from source code.
From the tool's definition The tool description states it "walks the given file or directory and detects which Nt/Zw functions are referenced" and "returns comma-separated list of detected NtFunction names." These are retrieval/analysis operations with no side effects.
Documented attack patterns abuse exactly the kind of access scan_ntfunctions 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 scan_ntfunctions:
{
"version": "1",
"default": "deny",
"tools": {
"scan_ntfunctions": {}
}
}scan_ntfunctions 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.
Scan source files for NtFunction / ZwFunction usage. Walks the given file or directory and detects which Nt/Zw functions are referenced. Useful for determining which syscalls your injection code needs. Supported file extensions: .h, .c, .cpp, .nim, .rs Args: search_path: Absolute path to a file or directory to scan. Returns: Comma-separated list of detected NtFunction names, or a message if none are found. 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 scan_ntfunctions: 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.
scan_ntfunctions 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 scan_ntfunctions 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 scan_ntfunctions. 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.
scan_ntfunctions 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.