get_media

View one media asset: its metadata, size, and (by default) content — UTF-8 for text/report assets, base64 for images — plus its revision history (prior versions with the prompts used). Pass a version id to view an archived revision instead of the current one; set withContent:false for metadata + ...

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

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/ai-featureboard-featureboard/get-media.md

WHAT IT DOES

What get_media does on FeatureBoard

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

RISK

Why get_media is rated Low

This tool only retrieves and queries existing media assets and their historical versions. It has no side effects, does not create, modify, delete, or execute external operations. It is a straightforward read operation on stored media metadata and content.

From the tool's definition Tool description states 'View one media asset: its metadata, size, and (by default) content' with explicit read-only operations: retrieves metadata, content in UTF-8 or base64, and revision history.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_media safely

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

get_media Allowed

get_media 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": {
    "get_media": {}
  }
}

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

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

FAQ

Questions about get_media

What does the get_media tool do? +

How do I enforce a policy on get_media? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for get_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 FeatureBoard. Nothing to install.

What risk level is get_media? +

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

Can I rate-limit get_media? +

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

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

get_media is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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