Low Risk

ism_get_devices

Get list of detected ISM band devices (weather stations, sensors, etc.)

How to control ism_get_devices ↓

What ism_get_devices does on AetherLink SDR MCP

AI agents call ism_get_devices to retrieve information from AetherLink SDR MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why ism_get_devices needs a policy

This tool performs a read-only operation by listing detected ISM band devices. It has no side effects, does not execute commands or control hardware, and does not modify any state. The passive nature of device detection and enumeration places it squarely in the Read category.

From the tool's definition Tool name 'ism_get_devices' and description 'Get list of detected ISM band devices' indicate a passive query operation that retrieves information about detected devices without modifying, executing, or controlling anything.

Documented attack patterns abuse exactly the kind of access ism_get_devices gives an agent:

How to control ism_get_devices

PolicyLayer is an MCP gateway — it sits between your AI agents and AetherLink SDR MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ism_get_devices:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ism_get_devices": {}
  }
}

ism_get_devices is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register AetherLink SDR MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ism_get_devices

What does the ism_get_devices tool do? +

Get list of detected ISM band devices (weather stations, sensors, etc.). It is categorised as a Read tool in the AetherLink SDR MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ism_get_devices? +

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

What risk level is ism_get_devices? +

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

Can I rate-limit ism_get_devices? +

Yes. Add a rate_limit block to the ism_get_devices 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 ism_get_devices completely? +

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

ism_get_devices is provided by the AetherLink SDR MCP server (n-erickson/aetherlink-sdr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AetherLink SDR MCP tool call.

Start from AetherLink SDR MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

26 AetherLink SDR MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.