Get a single Intercom article by ID. Returns full article details including title, body, author, and state.
AI agents call get_article to retrieve information from Intercom Articles MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries article data without creating, modifying, deleting, or executing any operations. It has no reversible or irreversible side effects. The blast radius of misuse is minimal — an agent could at worst read existing articles, which poses no data loss or system compromise risk.
From the tool's definition Tool description states 'Get a single Intercom article by ID. Returns full article details' — a retrieval operation with no side effects. The verb 'Get' and the action of returning article details indicate a read-only query.
Documented attack patterns abuse exactly the kind of access get_article gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intercom Articles MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_article:
{
"version": "1",
"default": "deny",
"tools": {
"get_article": {}
}
}get_article is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a single Intercom article by ID. Returns full article details including title, body, author, and state. It is categorised as a Read tool in the Intercom Articles MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intercom Articles MCP Server 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 Intercom Articles MCP Server. 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 Intercom Articles MCP Server MCP server (kaosensei/intercom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intercom Articles MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Intercom Articles MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.