currents.news.search
Search news articles by keyword across 70+ countries and 18+ languages. Returns full article text with Boolean operator support. Filter by language, country, category, and date range.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/currents.news.search.md
What currents.news.search does on Apibase
AI agents call currents.news.search to retrieve information from Apibase 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 |
|---|---|---|---|
country | string | — | ISO 3166-1 alpha-2 country code |
end_date | string | — | End date in ISO 8601 format |
keywords | string | Yes | Search keywords — supports Boolean operators (e.g. "AI agents", "climate AND policy") |
language | string | — | ISO 639-1 language code (e.g. "en", "es", "ar") |
page_size | integer | — | Number of articles to return, max 200 (default 10) |
start_date | string | — | Start date in ISO 8601 format (e.g. "2026-03-01T00:00:00+00:00") |
Parameters from the server's own tool schema.
Why currents.news.search is rated Low
Retrieves published news data with no modification, deletion, or execution capabilities.
From the tool's definition Search news articles, returns full article text, filter by parameters
Attacks that exploit this kind of access
The rule that runs currents.news.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For currents.news.search, this is the rule to start with:
currents.news.search 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 Apibase, apply this rule, and every currents.news.search call is checked against it from then on.
Questions about currents.news.search
Search news articles by keyword across 70+ countries and 18+ languages. Returns full article text with Boolean operator support. Filter by language, country, category, and date range. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
currents.news.search accepts 6 parameters: country, end_date, keywords, language, page_size, start_date. Required: keywords. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for currents.news.search: 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 Apibase. Nothing to install.
currents.news.search 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 currents.news.search 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 currents.news.search. 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.
currents.news.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue