project_close
Close the project in a session and release its single-writer lock.
This record as markdown: /tools/adr-fpga-bootstrap/project-close.md
What project_close does on Adr Fpga Bootstrap
AI agents use project_close to create or update resources in Adr Fpga Bootstrap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adr Fpga Bootstrap environment.
Why project_close is rated Medium
An AI agent can call project_close faster than any human can review: one bad instruction and it creates or modifies resources in Adr Fpga Bootstrap by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs project_close safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adr Fpga Bootstrap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_close, this is the rule to start with:
project_close stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adr Fpga Bootstrap, apply this rule, and every project_close call is checked against it from then on.
Questions about project_close
Close the project in a session and release its single-writer lock. It is categorised as a Write tool in the Adr Fpga Bootstrap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adr Fpga Bootstrap MCP server in PolicyLayer and add a rule for project_close: 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 Adr Fpga Bootstrap. Nothing to install.
project_close 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 project_close 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 project_close. 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.
project_close is provided by the Adr Fpga Bootstrap MCP server (zxyyz/adr-fpga-bootstrap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adr Fpga Bootstrap, and thousands of servers like it.
This server
Across the catalogue