get_article
Fetch a single article including its full markdown content, meta description, and tags. Use this when the user asks to "show me article X" or to review before editing. Set includeBlocks:true to also get the structured block body (heading / paragraph / image / list / quote / callout / table / code...
This record as markdown: /tools/a3plus-mcp/get-article.md
What get_article does on A3plus
AI agents call get_article to retrieve information from A3plus 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 |
|---|---|---|---|
siteId | string | Yes | The A3Plus site ID. |
articleId | string | Yes | The MongoDB ObjectId of the article (from list_articles or a previous create_article call). |
includeBlocks | boolean | — | Also return the structured `blocks` array and `contentVersion`. Off by default because it roughly doubles the response size. `blocks: null` means the article is |
Parameters from the server's own tool schema.
Why get_article is rated Low
Even though get_article only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_article safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_article, this is the rule to start with:
get_article 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 A3plus, apply this rule, and every get_article call is checked against it from then on.
Questions about get_article
Fetch a single article including its full markdown content, meta description, and tags. Use this when the user asks to "show me article X" or to review before editing. Set includeBlocks:true to also get the structured block body (heading / paragraph / image / list / quote / callout / table / code) — needed when you want to reason about or report on individual sections rather than the whole markdown blob. It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
get_article accepts 3 parameters: siteId, articleId, includeBlocks. Required: siteId, articleId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for get_article: 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 A3plus. Nothing to install.
get_article 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_article 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_article. 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_article is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue