get_topic_trends_attention

SERVERTanod SOURCEhttps://tanod.dev/mcp

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/get-topic-trends-attention.md

WHAT IT DOES

What get_topic_trends_attention does on Tanod

AI agents call get_topic_trends_attention to retrieve information from Tanod 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
`end`	object	—	Last day, YYYY-MM-DD (UTC), at most yesterday (later is clamped to it). Default: yesterday. The range is at most 365 days.
`start`	object	—	First day, YYYY-MM-DD (UTC). Default: 90 days ending at `end`.
`topics`	array	Yes	1 to 5 topics (words or a name, up to 100 characters each). Each is resolved to the top English Wikipedia search hit, reported as `article.title`. Several topic
`related`	object	—	Default false. True (one topic only) adds `related`: up to 10 `top` and 10 `rising` related Wikipedia topics, ranked by page views; not search queries and not G
`languages`	object	—	Optional Wikipedia language codes, at most 6 (en, de, ja ...). Default: en plus the four most-read languages that have the article. A language without the artic

Parameters from the server's own tool schema.

RISK

Why get_topic_trends_attention is rated Low

Even though get_topic_trends_attention only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_topic_trends_attention safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_topic_trends_attention, this is the rule to start with:

get_topic_trends_attention Allowed

get_topic_trends_attention is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_topic_trends_attention": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every get_topic_trends_attention call is checked against it from then on.

FAQ

Questions about get_topic_trends_attention

What does the get_topic_trends_attention tool do? +

utilpeek: Use when an agent must tell if interest in a topic is rising or fading: Wikipedia, Hacker News and news over time. For the articles use news_search. Returns daily topic trends for 1 to 5 topics: Wikipedia page views per language, Hacker News counts, news mentions, with 7- and 28-day change, spike days, direction and share. Not Google Trends data. Public attention signals, not Google Trends or search volume. related: related Wikipedia topics ranked by page views; not search queries and not Google Trends data. Topic = top English Wikipedia hit (see article.title). Complete days to yesterday; news only for the last 14 days. Cached 6 h. Bad input is a 422 and an upstream failure a 503 or 504 (not charged). Typically 3 to 15 s (first call for a topic; cached for 6 hours). Price: USD 0.005. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/topic-trends-attention-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does get_topic_trends_attention accept? +

get_topic_trends_attention accepts 5 parameters: end, start, topics, related, languages. Required: topics. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_topic_trends_attention? +

Register the Tanod MCP server in PolicyLayer and add a rule for get_topic_trends_attention: 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 Tanod. Nothing to install.

What risk level is get_topic_trends_attention? +

get_topic_trends_attention is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_topic_trends_attention? +

Yes. Add a rate_limit block to the get_topic_trends_attention 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.

How do I block get_topic_trends_attention completely? +

Set action: deny in the PolicyLayer policy for get_topic_trends_attention. 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.

What MCP server provides get_topic_trends_attention? +

get_topic_trends_attention is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tanod, and thousands of servers like it.

This server

All 308 Tanod tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →