list_blog_posts
List editorial blog articles (excerpts). Use get_blog_post for full content. Filter by category, cancer-type tag, or keyword.
This record as markdown: /tools/io-github-hifarrer-cure-cancer-with-ai/list-blog-posts.md
What list_blog_posts does on Cure Cancer With AI
AI agents call list_blog_posts to retrieve information from Cure Cancer With AI 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 | integer | — | Results per page (1–100, default 20). |
offset | integer | — | Number of results to skip (default 0). |
search | string | — | Keyword search across title, excerpt, and content. |
category | string | — | Filter by primary category. |
cancerType | string | — | Filter by cancer-type tag. |
Parameters from the server's own tool schema.
Why list_blog_posts is rated Low
This tool retrieves and lists existing blog post data with optional filters, returning excerpts without side effects. It is purely informational and read-only, with minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_blog_posts' and description 'List editorial blog articles (excerpts)' with filtering options indicate a retrieval-only operation. No creation, modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs list_blog_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cure Cancer With AI, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_blog_posts, this is the rule to start with:
list_blog_posts 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 Cure Cancer With AI, apply this rule, and every list_blog_posts call is checked against it from then on.
Questions about list_blog_posts
List editorial blog articles (excerpts). Use get_blog_post for full content. Filter by category, cancer-type tag, or keyword. It is categorised as a Read tool in the Cure Cancer With AI MCP Server, which means it retrieves data without modifying state.
list_blog_posts accepts 5 parameters: limit, offset, search, category, cancerType. The full parameter table on this page comes from the server's own tool schema.
Register the Cure Cancer With AI MCP server in PolicyLayer and add a rule for list_blog_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 Cure Cancer With AI. Nothing to install.
list_blog_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 list_blog_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 list_blog_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.
list_blog_posts is provided by the Cure Cancer With AI MCP server (https://www.curecancerwithai.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cure Cancer With AI, and thousands of servers like it.
This server
Across the catalogue