oe_collections_sync_history
Paginate /api/article/list and upsert chats. Incremental by default (stops on the first all-known page).
This record as markdown: /tools/htlin222-openevidence-mcp/oe-collections-sync-history.md
What oe_collections_sync_history does on :
AI agents use oe_collections_sync_history to create or update resources in :, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your : environment.
Why oe_collections_sync_history is rated Medium
The tool both reads (paginates article list) and writes (upserts chats/articles into a local store). Since upsert is a write/create-or-update operation, the most severe applicable category is Write. The blast radius is medium because it can bulk-modify many records incrementally, but changes are reversible in principle.
From the tool's definition 'upsert chats' — upsert is a create-or-update operation that modifies data; 'Paginate /api/article/list' retrieves articles to drive the sync
Attacks that exploit this kind of access
The rule that runs oe_collections_sync_history 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_collections_sync_history, this is the rule to start with:
oe_collections_sync_history stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_collections_sync_history call is checked against it from then on.
Questions about oe_collections_sync_history
Paginate /api/article/list and upsert chats. Incremental by default (stops on the first all-known page). It is categorised as a Write tool in the : MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the : MCP server in PolicyLayer and add a rule for oe_collections_sync_history: 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_collections_sync_history is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the oe_collections_sync_history 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_collections_sync_history. 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_collections_sync_history 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