Low Risk

list_iterators

List all 7 available syscall iterators with descriptions. Each iterator implements a different strategy for resolving syscall numbers at runtime from the in-memory ntdll.dll image. Returns: Formatted list of iterators with their descriptions.

How to control list_iterators ↓

AI agents call list_iterators 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 performs a retrieval operation only. It queries and returns information about syscall iterator implementations without creating, modifying, deleting, executing, or moving any resources. The tool has no side effects and poses minimal security risk as an unauthorized disclosure vector. It is informational in nature, serving to enumerate available options to the user.

From the tool's definition Tool name is 'list_iterators' and description states it 'List all 7 available syscall iterators with descriptions.' The verb 'list' combined with 'returns formatted list' indicates a read-only query operation that retrieves and displays information about…

Documented attack patterns abuse exactly the kind of access list_iterators 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_iterators:

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

list_iterators 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_iterators tool do? +

List all 7 available syscall iterators with descriptions. Each iterator implements a different strategy for resolving syscall numbers at runtime from the in-memory ntdll.dll image. Returns: Formatted list of iterators with their descriptions. 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_iterators? +

Register the Sysplant MCP server in PolicyLayer and add a rule for list_iterators: 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_iterators? +

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

Can I rate-limit list_iterators? +

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

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

list_iterators 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.