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 | Yes | |
api_key | string | — | |
entry_ids | array | — | |
stream_id | string | — |
Parameters from the server's own tool schema.
Most sub-actions are read-only (get_feedly_feeds, get_feedly_streams, search_feedly, get_feedly_categories), but 'mark_as_read' writes/modifies state in the Feedly account. Per the rules, the most severe applicable category applies, making this Write. Severity is medium since misuse could bulk-mark articles as read, losing track of unread content, but no irreversible data loss or financial impact.
From the tool's definition mark_as_read — modifies read/unread state of feed items in Feedly
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
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. Required: action. 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 (@unclick/mcp-server). 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 →