Get full article content by ID. Use AFTER browsing titles with get_content/search_articles. Token-efficient workflow: (1) browse titles only, (2) identify interesting articles, (3) fetch full content for selected articles. Returns single article with complete text, metadata, and excerpt.
AI agents call get_article_full to retrieve information from MCP RSS 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 from an RSS feed management system with no side effects. It reads existing content without creating, modifying, deleting, or executing anything. The workflow context confirms it is used after identifying articles of interest, purely for content retrieval. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'get_article_full' and description states it 'Get full article content by ID' and 'Returns single article with complete text, metadata, and excerpt.' The description explicitly frames this as part of a browsing workflow with no modification,…
Attacks that exploit this kind of access
Get full article content by ID. Use AFTER browsing titles with get_content/search_articles. Token-efficient workflow: (1) browse titles only, (2) identify interesting articles, (3) fetch full content for selected articles. Returns single article with complete text, metadata, and excerpt. It is categorised as a Read tool in the MCP RSS MCP Server, which means it retrieves data without modifying state.
Register the MCP RSS MCP server in PolicyLayer and add a rule for get_article_full: 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 MCP RSS. Nothing to install.
get_article_full 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_full 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_full. 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_full is provided by the MCP RSS MCP server (ronnycoding/my_mcp_rss). 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 →