AI agents call get_event_feedback_prompt to retrieve information from Events 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 | Yes | |
attended_at | string | — | Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend. |
Parameters from the server's own tool schema.
This tool retrieves a feedback prompt/questionnaire for display purposes. It has no side effects beyond reading data from the Events server. It does not create, modify, or delete records (the description says 'before recording feedback', implying the actual recording happens separately). It does not execute code or trigger external operations. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'get_event_feedback_prompt' and description 'ask a short post-event follow-up before recording feedback' indicates retrieval of a prompt template or questionnaire.
Attacks that exploit this kind of access
Use this when a user previously picked or attended a UPlayground event and the assistant should ask a short post-event follow-up before recording feedback. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
get_event_feedback_prompt accepts 2 parameters: event_id, attended_at. Required: event_id. The full parameter table on this page comes from the server's own tool schema.
Register the Events MCP server in PolicyLayer and add a rule for get_event_feedback_prompt: 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 Events. Nothing to install.
get_event_feedback_prompt 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_feedback_prompt 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_feedback_prompt. 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_feedback_prompt is provided by the Events MCP server (uplayground-events). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_event_feedback_prompt is one line of Events's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →