Start the first-stage requirements intake and write requirements.yaml plus questionnaire markdown.
AI agents use vivado_start_requirements_intake to create or update resources in Vivado Mcp Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vivado Mcp Agent environment.
This tool writes files (requirements.yaml and a questionnaire markdown file) to disk as part of a project setup workflow. It creates new files but does not execute code, delete data, or involve financial transactions. The blast radius is low since it only creates project configuration/documentation files.
From the tool's definition 'Start the first-stage requirements intake and write requirements.yaml plus questionnaire markdown'
Attacks that exploit this kind of access
Start the first-stage requirements intake and write requirements.yaml plus questionnaire markdown. It is categorised as a Write tool in the Vivado Mcp Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vivado Mcp Agent MCP server in PolicyLayer and add a rule for vivado_start_requirements_intake: 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 Vivado Mcp Agent. Nothing to install.
vivado_start_requirements_intake is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the vivado_start_requirements_intake 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 vivado_start_requirements_intake. 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.
vivado_start_requirements_intake is provided by the Vivado Mcp Agent MCP server (wangyuxin0707/vivado-mcp-agent). 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 →