search_media

Search/filter a project

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/search-media.md

WHAT IT DOES

What search_media does on FeatureBoard

AI agents call search_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 search_media is rated Low

This tool performs search and filtering operations on project data, which are read-only operations. There are no side effects, no data is modified or deleted, and no external operations are triggered. The blast radius of misuse is minimal—an agent might retrieve unintended project information, but this poses low risk.

From the tool's definition Tool name 'search_media' combined with description 'Search/filter a project' indicates retrieval and querying operations with no data modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_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 search_media, this is the rule to start with:

search_media Allowed

search_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": {
    "search_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 search_media call is checked against it from then on.

FAQ

Questions about search_media

What does the search_media tool do? +

Search/filter a project. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_media? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for search_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 search_media? +

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

Can I rate-limit search_media? +

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

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

search_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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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