device_crawl_api
Discover available methods and properties on selected actors via API crawl.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/device-crawl-api.md
What device_crawl_api does on Uefn
AI agents call device_crawl_api to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why device_crawl_api is rated Low
This tool queries metadata about actor APIs to enumerate available methods and properties. It is informational only, returning data about the actor's interface without side effects. This fits the Read category (retrieves or queries data; no side effects). The low severity reflects minimal blast radius — misuse would only expose metadata, not corrupt data or trigger unwanted actions.
From the tool's definition Tool performs 'Discover available methods and properties on selected actors via API crawl' — a pure discovery/inspection operation that introspects existing actor definitions without modifying state, creating resources, or executing arbitrary code.
Attacks that exploit this kind of access
The rule that runs device_crawl_api safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device_crawl_api, this is the rule to start with:
device_crawl_api 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 Uefn, apply this rule, and every device_crawl_api call is checked against it from then on.
Questions about device_crawl_api
Discover available methods and properties on selected actors via API crawl. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for device_crawl_api: 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 Uefn. Nothing to install.
device_crawl_api 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 device_crawl_api 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 device_crawl_api. 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.
device_crawl_api is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue