Low Risk

mediaGet

Get media with id

How to control mediaGet ↓

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

Low Risk

This tool retrieves media by identifier, which is a read-only query operation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an attacker could only access media they have permission to retrieve, which is a standard read operation risk.

From the tool's definition Tool name 'mediaGet' and description 'Get media with id' indicate a retrieval operation with no modification or side effects.

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

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

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

mediaGet 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 Mcp Taskade — 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.

Go deeper

What does the mediaGet tool do? +

Get media with id. It is categorised as a Read tool in the Mcp Taskade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mediaGet? +

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

What risk level is mediaGet? +

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

Can I rate-limit mediaGet? +

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

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

mediaGet is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Taskade tool call.

Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ 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.