full_text_search

What full_text_search does on Mcpg

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

Why full_text_search is rated Low

Full-text search tools retrieve matching records from a database but do not create, modify, delete, or execute arbitrary operations. This is consistent with Read category operations like search, list, get, fetch. The lack of description slightly reduces confidence but the tool name strongly indicates retrieval semantics. Blast radius is low as misuse would only expose existing data, not modify or harm system state.

From the tool's definition Tool name 'full_text_search' indicates a search operation that retrieves/queries data without modification. No description provided, but the naming convention aligns with standard read-only search operations common in database MCP servers.

The rule that runs full_text_search safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "full_text_search": {}
  }
}

Questions about full_text_search