Get public workflow events.
AI agents call get_workflow_events to retrieve information from MCP for Vivado without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workflow event data without altering state, triggering external operations, or performing destructive actions. Accessing public events has minimal risk; the worst outcome would be information disclosure of already-public data. Classified as Read with low severity.
From the tool's definition Tool name 'get_workflow_events' combined with description 'Get public workflow events' indicates a retrieval operation. The verb 'Get' and the qualifier 'public' demonstrate read-only intent with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Get public workflow events. It is categorised as a Read tool in the MCP for Vivado MCP Server, which means it retrieves data without modifying state.
Register the MCP for Vivado MCP server in PolicyLayer and add a rule for get_workflow_events: 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 MCP for Vivado. Nothing to install.
get_workflow_events 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_workflow_events 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_workflow_events. 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_workflow_events is provided by the MCP for Vivado MCP server (lzw12123/mcp-for-vivado). 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 →