search_descriptions

Search RSS feed entries by description/content

SERVERContextForge MCP Gateway SOURCEjrmatherly/mcp-context-forge

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/jrmatherly-mcp-context-forge/search-descriptions.md

WHAT IT DOES

What search_descriptions does on ContextForge MCP Gateway

AI agents call search_descriptions to retrieve information from ContextForge MCP Gateway 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_descriptions is rated Low

This tool retrieves and searches existing RSS feed data based on description/content criteria. It performs a read-only query with no capability to create, modify, delete, or execute external operations. The blast radius is minimal — misuse would only return unwanted search results, not cause data loss or execute code.

From the tool's definition Tool name is 'search_descriptions' and description states it 'Search[es] RSS feed entries by description/content' — a query operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_descriptions safely

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

search_descriptions Allowed

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

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

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

FAQ

Questions about search_descriptions

What does the search_descriptions tool do? +

Search RSS feed entries by description/content. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_descriptions? +

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

What risk level is search_descriptions? +

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

Can I rate-limit search_descriptions? +

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

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

search_descriptions is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ContextForge MCP Gateway, and thousands of servers like it.

This server

All 221 ContextForge MCP Gateway 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 →