Get full details for a specific Tekna event.
AI agents call get_event_details to retrieve information from Tekna Events & News without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries event information without creating, modifying, deleting, or executing any operations. It is a pure read operation that has no blast radius if misused by an AI agent—at worst, an agent could retrieve event details it shouldn't have access to, but this is an authorization concern rather than a security category concern. The tool itself is passive and informational.
From the tool's definition Tool name 'get_event_details' and description 'Get full details for a specific Tekna event' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get full details for a specific Tekna event. It is categorised as a Read tool in the Tekna Events & News MCP Server, which means it retrieves data without modifying state.
Register the Tekna Events & News MCP server in PolicyLayer and add a rule for get_event_details: 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 Tekna Events & News. Nothing to install.
get_event_details 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 get_event_details 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 get_event_details. 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.
get_event_details is provided by the Tekna Events & News MCP server (pypi:mcp-tekna). 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 →