List released v2 public FPGA MCP methods.
AI agents call list_public_methods 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 or lists metadata about available public methods in the FPGA MCP interface. It has no side effects, does not execute hardware workflows, does not modify data, and does not trigger synthesis or implementation. It is purely informational, making it a Read category tool with low severity and high confidence.
From the tool's definition Tool name 'list_public_methods' and description 'List released v2 public FPGA MCP methods' indicate a query/retrieval operation that enumerates available API methods without modifying state.
Attacks that exploit this kind of access
List released v2 public FPGA MCP methods. 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 list_public_methods: 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.
list_public_methods 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 list_public_methods 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 list_public_methods. 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.
list_public_methods 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 →