find_device

Find a single device by serial number. Returns the device record or None.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/find-device.md

WHAT IT DOES

What find_device does on API-Central

AI agents call find_device to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_device is rated Low

This tool retrieves device information by serial number and returns data without creating, modifying, deleting, or executing operations. It is a pure read operation with minimal risk—device metadata is typically non-sensitive operational information. The 'Returns the device record or None' phrasing confirms it only retrieves and does not alter state.

From the tool's definition Tool name 'find_device' and description 'Find a single device by serial number. Returns the device record or None.' indicate a lookup/query operation with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_device safely

PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_device, this is the rule to start with:

find_device Allowed

find_device is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_device": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every find_device call is checked against it from then on.

FAQ

Questions about find_device

What does the find_device tool do? +

Find a single device by serial number. Returns the device record or None. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_device? +

Register the API-Central MCP server in PolicyLayer and add a rule for find_device: 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 API-Central. Nothing to install.

What risk level is find_device? +

find_device is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_device? +

Yes. Add a rate_limit block to the find_device 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.

How do I block find_device completely? +

Set action: deny in the PolicyLayer policy for find_device. 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.

What MCP server provides find_device? +

find_device is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →