contentful_list_entries
List Contentful entries, optionally filtered by content_type or full-text query.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/contentful-list-entries.md
What contentful_list_entries does on UnClick
AI agents call contentful_list_entries to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Entries to return (max 100, default 25) |
query | string | — | Full-text search query |
space_id | string | — | Contentful space id (can be a saved default) |
environment | string | — | Environment (default master) |
access_token | string | Yes | Contentful Content Delivery API token |
content_type | string | — | Filter to one content type id |
Parameters from the server's own tool schema.
Why contentful_list_entries is rated Low
This tool retrieves and lists entries from a Contentful CMS without creating, modifying, or deleting data. It performs a read-only query operation with no side effects. The blast radius of misuse is low—an agent could retrieve unintended content, but cannot alter or delete it.
From the tool's definition Tool description states 'List Contentful entries' with optional filtering by content_type or full-text query. The verb 'list' and 'query' indicate data retrieval with no modification.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs contentful_list_entries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contentful_list_entries, this is the rule to start with:
contentful_list_entries 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 UnClick, apply this rule, and every contentful_list_entries call is checked against it from then on.
Questions about contentful_list_entries
List Contentful entries, optionally filtered by content_type or full-text query. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
contentful_list_entries accepts 6 parameters: limit, query, space_id, environment, access_token, content_type. Required: access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for contentful_list_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 UnClick. Nothing to install.
contentful_list_entries 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 contentful_list_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.
Set action: deny in the PolicyLayer policy for contentful_list_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.
contentful_list_entries is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue