List all 4 available syscall caller stub methods with descriptions. Each method defines how the resolved syscall is actually executed, trading off between simplicity and evasion capability. Returns: Formatted list of methods with their descriptions.
AI agents call list_methods 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 presents informational data about available syscall methods. It performs no code generation, execution, modification, or deletion. Even in the context of a syscall generation server, listing available options is a read-only enumeration operation. No state is changed, no code is executed, and no data is modified. The tool is purely informational.
From the tool's definition Tool name 'list_methods' combined with description stating it 'List[s] all 4 available syscall caller stub methods with descriptions' and 'Returns: Formatted list of methods with their descriptions.' The verb 'List' and action of returning information…
Documented attack patterns abuse exactly the kind of access list_methods 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_methods:
{
"version": "1",
"default": "deny",
"tools": {
"list_methods": {}
}
}list_methods 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 4 available syscall caller stub methods with descriptions. Each method defines how the resolved syscall is actually executed, trading off between simplicity and evasion capability. Returns: Formatted list of methods with their descriptions. 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_methods: 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_methods 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_methods 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_methods. 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_methods 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.