wordlist_get
Retrieve a specific wordlist entry by its ID.
This record as markdown: /tools/nyxstrike/wordlist-get.md
What wordlist_get does on Nyxstrike
AI agents call wordlist_get to retrieve information from Nyxstrike without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wordlist_get is rated Low
This tool performs data retrieval only. It fetches a wordlist entry by identifier, which is a passive Read operation with no capability to modify, delete, or execute code. While hosted on a penetration testing platform, the tool itself is non-destructive and informational. Severity is low because retrieval of wordlist data has minimal blast radius and no irreversible consequences.
From the tool's definition Tool description states 'Retrieve a specific wordlist entry by its ID' — a read-only operation that queries data without side effects.
Attacks that exploit this kind of access
The rule that runs wordlist_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nyxstrike, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wordlist_get, this is the rule to start with:
wordlist_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nyxstrike, apply this rule, and every wordlist_get call is checked against it from then on.
Questions about wordlist_get
Retrieve a specific wordlist entry by its ID. It is categorised as a Read tool in the Nyxstrike MCP Server, which means it retrieves data without modifying state.
Register the Nyxstrike MCP server in PolicyLayer and add a rule for wordlist_get: 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 Nyxstrike. Nothing to install.
wordlist_get 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 wordlist_get 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 wordlist_get. 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.
wordlist_get is provided by the Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nyxstrike, and thousands of servers like it.
This server
Across the catalogue