List all available sensor nodes and their last activity
AI agents call list_available_nodes to retrieve information from Sage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of sensor node metadata and status. It retrieves existing data about available nodes and their activity timestamps with no side effects, data modification, code execution, or resource destruction. The blast radius of misuse is minimal—an agent could only learn about available infrastructure.
From the tool's definition Tool name 'list_available_nodes' and description 'List all available sensor nodes and their last activity' indicate a query operation that retrieves information about nodes without modifying or executing any actions.
Attacks that exploit this kind of access
List all available sensor nodes and their last activity. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for list_available_nodes: 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 Sage MCP Server. Nothing to install.
list_available_nodes 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_available_nodes 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_available_nodes. 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_available_nodes is provided by the Sage MCP Server MCP server (waggle-sensor/sage-mcp). 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 →