Low Risk

list_device_media

list_device_media

How to control list_device_media ↓

What list_device_media does on Safie API MCP Server

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

Low Risk

Why list_device_media needs a policy

The tool retrieves/lists media from Safie devices without modifying or deleting data. This is a read-only query operation consistent with other data retrieval tools on the server. Even if an AI agent overuses this, it only fetches existing data with no side effects or destructive capability.

From the tool's definition Tool name 'list_device_media' combined with server description stating it 'retrieve[s]...media' from Safie API. Sibling tools ('list_devices', 'list_device_standard_events', 'get_device_image', 'get_device_thumbnail') are all read operations.

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

How to control list_device_media

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

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

list_device_media 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 Safie API MCP Server — 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 list_device_media

What does the list_device_media tool do? +

list_device_media. It is categorised as a Read tool in the Safie API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_device_media? +

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

What risk level is list_device_media? +

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

Can I rate-limit list_device_media? +

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

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

list_device_media is provided by the Safie API MCP Server MCP server (safiepublic/safie-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Safie API MCP Server tool call.

Start from Safie API MCP Server, 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.

6 Safie API MCP Server 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.