feedly_action
Perform a Feedly action: get_feedly_feeds, get_feedly_streams, search_feedly, get_feedly_categories, mark_as_read.
This record as markdown: /tools/creativelead-unclick/feedly-action.md
What feedly_action does on UnClick
AI agents use feedly_action to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
count | number | — | |
query | string | — | |
action | string | — | |
api_key | string | — | |
entry_ids | array | — | |
stream_id | string | — |
Parameters from the server's own tool schema.
Why feedly_action is rated Medium
Most actions (get_feedly_feeds, get_feedly_streams, search_feedly, get_feedly_categories) are Read operations, but 'mark_as_read' constitutes a state-modifying Write operation. Per the severity rules, the most severe applicable category wins, making this a Write. Severity is medium because marking items as read is reversible in principle but could affect content management workflows if misused at scale.
From the tool's definition mark_as_read action listed in the tool description — this modifies the read/unread state of items in Feedly
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs feedly_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For feedly_action, this is the rule to start with:
feedly_action 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 UnClick, apply this rule, and every feedly_action call is checked against it from then on.
Questions about feedly_action
Perform a Feedly action: get_feedly_feeds, get_feedly_streams, search_feedly, get_feedly_categories, mark_as_read. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
feedly_action accepts 6 parameters: count, query, action, api_key, entry_ids, stream_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for feedly_action: 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 UnClick. Nothing to install.
feedly_action 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 feedly_action 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 feedly_action. 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.
feedly_action is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue