Fetch posts directly from Contentful CMS (if configured)
AI agents call get_contentful_posts to retrieve information from V2 Ai Insights Scraper MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves blog post data from a Contentful CMS without modifying, deleting, or executing operations. It is a straightforward read operation with no side effects. Severity is low because unauthorized access would expose public blog content with limited blast radius, and the tool operates within the intended scraper functionality.
From the tool's definition Tool name 'get_contentful_posts' and description 'Fetch posts directly from Contentful CMS' indicate data retrieval only. The verb 'Fetch' and context of a scraper MCP server confirm read-only query operations.
Attacks that exploit this kind of access
Fetch posts directly from Contentful CMS (if configured). It is categorised as a Read tool in the V2 Ai Insights Scraper MCP MCP Server, which means it retrieves data without modifying state.
Register the V2 Ai Insights Scraper MCP server in PolicyLayer and add a rule for get_contentful_posts: 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 V2 Ai Insights Scraper MCP. Nothing to install.
get_contentful_posts 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 get_contentful_posts 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 get_contentful_posts. 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.
get_contentful_posts is provided by the V2 Ai Insights Scraper MCP server (v2-digital/v2-ai-mcp). 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 →