search_entities_with_query

Search entities using query test. Use query params from and size for pagination. Use sort_field to sort the results in sort_order.

Server Mcp Openmetadata pfldy2850/mcp-openmetadata
Category Read
Risk class Low
Parameters 00 required

What search_entities_with_query does on Mcp Openmetadata

AI agents call search_entities_with_query to retrieve information from Mcp Openmetadata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_entities_with_query needs a policy

This tool retrieves and queries metadata from OpenMetadata (tables, columns, ownership information) with no capability to create, modify, or delete data. The use of pagination (from/size) and sorting (sort_field/sort_order) parameters is characteristic of a read-only search operation. There are no side effects or data mutations possible with this tool.

From the tool's definition Tool description states 'Search entities using query test' with pagination and sorting parameters. The name 'search_entities_with_query' and sibling tools like 'get_list_of_tables', 'get_sample_data', 'get_table_by_fqn' all indicate data retrieval operations…

Questions about search_entities_with_query

What does the search_entities_with_query tool do? +

Search entities using query test. Use query params from and size for pagination. Use sort_field to sort the results in sort_order. It is categorised as a Read tool in the Mcp Openmetadata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_entities_with_query? +

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

What risk level is search_entities_with_query? +

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

Can I rate-limit search_entities_with_query? +

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

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

search_entities_with_query is provided by the Mcp Openmetadata MCP server (pfldy2850/mcp-openmetadata). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.