Low Risk

query_entries

Query and find content in Contentful delivery API

How to control query_entries ↓

What query_entries does on Contentful Delivery MCP Server

AI agents call query_entries to retrieve information from Contentful Delivery MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query_entries needs a policy

This tool retrieves or queries content from Contentful's Delivery API with no side effects. It does not create, modify, delete, or execute code—it only searches and fetches data. The Delivery API itself is designed for read-only access to published content, making this a clear Read operation with low severity and blast radius.

From the tool's definition Tool description states 'Query and find content' in the Contentful Delivery API. The server description confirms this is for 'query' operations.

Documented attack patterns abuse exactly the kind of access query_entries gives an agent:

How to control query_entries

PolicyLayer is an MCP gateway — it sits between your AI agents and Contentful Delivery MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_entries:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_entries": {}
  }
}

query_entries is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Contentful Delivery MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_entries

What does the query_entries tool do? +

Query and find content in Contentful delivery API. It is categorised as a Read tool in the Contentful Delivery MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_entries? +

Register the Contentful Delivery MCP Server MCP server in PolicyLayer and add a rule for query_entries: 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 Contentful Delivery MCP Server. Nothing to install.

What risk level is query_entries? +

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

Can I rate-limit query_entries? +

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

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

query_entries is provided by the Contentful Delivery MCP Server MCP server (mshaaban0/contentful-delivery-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Contentful Delivery MCP Server tool call.

Start from Contentful Delivery MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 Contentful Delivery MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.