Agent discovery for autonomous workflows. Get system capabilities and available endpoints.
AI agents call nwo_agent_discovery to retrieve information from NWO Robotics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about system capabilities and available endpoints for discovery purposes. It is a passive read operation that does not create, modify, delete, or execute any actions on robots, IoT devices, or financial systems. The lack of side effects and its role in information gathering places it firmly in the Read category with low severity.
From the tool's definition Tool name 'nwo_agent_discovery' and description 'Get system capabilities and available endpoints' indicate a query/retrieval operation with no data modification or external effects.
Attacks that exploit this kind of access
Agent discovery for autonomous workflows. Get system capabilities and available endpoints. It is categorised as a Read tool in the NWO Robotics MCP Server, which means it retrieves data without modifying state.
Register the NWO Robotics MCP server in PolicyLayer and add a rule for nwo_agent_discovery: 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 NWO Robotics. Nothing to install.
nwo_agent_discovery 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 nwo_agent_discovery 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 nwo_agent_discovery. 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.
nwo_agent_discovery is provided by the NWO Robotics MCP server (redciprianpater/mcp-server-robotics). 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 →