mysql_fulltext_expand
Perform FULLTEXT search WITH QUERY EXPANSION for finding related terms.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-fulltext-expand.md
What mysql_fulltext_expand does on Mysql Mcp
AI agents call mysql_fulltext_expand to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_fulltext_expand is rated Low
FULLTEXT search with query expansion is a search/retrieval operation that returns results without modifying data or executing arbitrary code. It falls squarely into the Read category. Severity is low because the tool only queries data and cannot cause side effects or data loss. High confidence (0.95) due to clear evidence from the description of a read-only search function.
From the tool's definition Tool description: 'Perform FULLTEXT search WITH QUERY EXPANSION for finding related terms.' The tool performs a FULLTEXT search operation, which is a read-only query that retrieves matching records based on search expansion logic.
Attacks that exploit this kind of access
The rule that runs mysql_fulltext_expand safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_fulltext_expand, this is the rule to start with:
mysql_fulltext_expand is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_fulltext_expand call is checked against it from then on.
Questions about mysql_fulltext_expand
Perform FULLTEXT search WITH QUERY EXPANSION for finding related terms. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_fulltext_expand: 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 Mysql Mcp. Nothing to install.
mysql_fulltext_expand is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mysql_fulltext_expand 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.
Set action: deny in the PolicyLayer policy for mysql_fulltext_expand. 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.
mysql_fulltext_expand is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue