Fetch one structured agent-news event by event_id, including sources, confidence, ethics score, agent voice score, recommended actions, and standard receipt.
AI agents call tat_get_event to retrieve information from The Agent Times without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | — | Agent event id |
Parameters from the server's own tool schema.
Even though tat_get_event 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.
Documented attack patterns abuse exactly the kind of access tat_get_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and The Agent Times, and nothing reaches the server without passing your rules. This is the rule we recommend for tat_get_event:
{
"version": "1",
"default": "deny",
"tools": {
"tat_get_event": {}
}
}tat_get_event is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch one structured agent-news event by event_id, including sources, confidence, ethics score, agent voice score, recommended actions, and standard receipt. It is categorised as a Read tool in the The Agent Times MCP Server, which means it retrieves data without modifying state.
tat_get_event accepts 1 parameter: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the The Agent Times MCP server in PolicyLayer and add a rule for tat_get_event: 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 The Agent Times. Nothing to install.
tat_get_event 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 tat_get_event 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 tat_get_event. 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.
tat_get_event is provided by the The Agent Times MCP server (theagenttimes/news). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 The Agent Times tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 The Agent Times tools catalogued and risk-classified — across an index of 42,500+ MCP servers.