Search and filter Drupal content by type. Returns a list of nodes matching the criteria.
AI agents call query_content to retrieve information from Drupal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing content without modifying, deleting, or executing operations. It is a standard read operation that returns data based on search criteria. The low severity reflects minimal blast radius—misuse would only expose or over-retrieve content visibility rather than cause data loss, financial impact, or system compromise.
From the tool's definition Tool description states it "Search and filter Drupal content by type" and "Returns a list of nodes matching the criteria." The server description emphasizes "querying, searching, and retrieving content" with no mention of modification, deletion, or execution…
Attacks that exploit this kind of access
Search and filter Drupal content by type. Returns a list of nodes matching the criteria. It is categorised as a Read tool in the Drupal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Drupal MCP Server MCP server in PolicyLayer and add a rule for query_content: 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 Drupal MCP Server. Nothing to install.
query_content 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 query_content 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 query_content. 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.
query_content is provided by the Drupal MCP Server MCP server (peximo/drupal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →