oe_article_get
Fetch an article (answer) by id or /ask/ URL — the fetch-later half of fire-and-forget oe_ask.
This record as markdown: /tools/htlin222-openevidence-mcp/oe-article-get.md
What oe_article_get does on :
AI agents call oe_article_get to retrieve information from : without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why oe_article_get is rated Low
oe_article_get retrieves article data by identifier. This is a read-only query operation that returns existing data without creating, modifying, deleting, or executing external operations. Even if misused by an agent, the worst outcome is accessing unintended article content, which is a low-severity information disclosure risk.
From the tool's definition Tool description states 'Fetch an article (answer) by id' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs oe_article_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and :, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For oe_article_get, this is the rule to start with:
oe_article_get 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 :, apply this rule, and every oe_article_get call is checked against it from then on.
Questions about oe_article_get
Fetch an article (answer) by id or /ask/ URL — the fetch-later half of fire-and-forget oe_ask. It is categorised as a Read tool in the : MCP Server, which means it retrieves data without modifying state.
Register the : MCP server in PolicyLayer and add a rule for oe_article_get: 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 :. Nothing to install.
oe_article_get 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 oe_article_get 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 oe_article_get. 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.
oe_article_get is provided by the : MCP server (htlin222/openevidence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on :, and thousands of servers like it.
This server
Across the catalogue