get_blog_post
Fetch a single blog post by slug, including the full article content.
This record as markdown: /tools/io-github-hifarrer-cure-cancer-with-ai/get-blog-post.md
What get_blog_post does on Cure Cancer With AI
AI agents call get_blog_post 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 |
|---|---|---|---|
slug | string | Yes | Blog post slug, e.g. "immunotherapy-breakthroughs". |
Parameters from the server's own tool schema.
Why get_blog_post is rated Low
This tool retrieves and queries blog post content based on a slug identifier. It performs a read-only operation that returns existing data without creating, modifying, deleting, or executing any operations. The action is a straightforward fetch with no side effects, aligning clearly with the Read category.
From the tool's definition Tool name 'get_blog_post' and description 'Fetch a single blog post by slug, including the full article content' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_blog_post 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 get_blog_post, this is the rule to start with:
get_blog_post 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 get_blog_post call is checked against it from then on.
Questions about get_blog_post
Fetch a single blog post by slug, including the full article content. It is categorised as a Read tool in the Cure Cancer With AI MCP Server, which means it retrieves data without modifying state.
get_blog_post accepts 1 parameter: slug. Required: slug. 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 get_blog_post: 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.
get_blog_post 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_blog_post 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_blog_post. 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_blog_post 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