guardian_search_articles
Search for articles on The Guardian.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/guardian-search-articles.md
What guardian_search_articles does on UnClick
AI agents call guardian_search_articles to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | |
api_key | string | — | |
section | string | — | |
to_date | string | — | |
from_date | string | — | |
page_size | number | — |
Parameters from the server's own tool schema.
Why guardian_search_articles is rated Low
This tool performs a query operation that retrieves publicly available article data from The Guardian's service. It has no side effects, does not modify data, execute code, delete content, or move money. It is a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'guardian_search_articles' and description 'Search for articles on The Guardian' indicate a search/retrieval operation with no modification or destructive capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs guardian_search_articles 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 guardian_search_articles, this is the rule to start with:
guardian_search_articles 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 UnClick, apply this rule, and every guardian_search_articles call is checked against it from then on.
Questions about guardian_search_articles
Search for articles on The Guardian. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
guardian_search_articles accepts 6 parameters: q, api_key, section, to_date, from_date, page_size. Required: q. 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 guardian_search_articles: 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.
guardian_search_articles 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 guardian_search_articles 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 guardian_search_articles. 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.
guardian_search_articles 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue