AI agents call explain_setup to retrieve information from Nubis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explains setup requirements and implementation steps for a feature. This is a read/query operation that retrieves or generates informational content with no side effects. It does not modify, execute, or delete any data.
From the tool's definition 'Explain setup and what needs to be done for feature to be implemented' — purely explanatory/informational output
Attacks that exploit this kind of access
Explain setup and what needs to be done for feature to be implemented. It is categorised as a Read tool in the Nubis MCP Server, which means it retrieves data without modifying state.
Register the Nubis MCP server in PolicyLayer and add a rule for explain_setup: 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 Nubis. Nothing to install.
explain_setup 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 explain_setup 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 explain_setup. 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.
explain_setup is provided by the Nubis MCP server (@lil2good/nubis-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →