AI agents invoke gigaspec-wizard to trigger actions in Gigaspec. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool actively runs an interactive wizard process that executes a guided workflow, potentially triggering further analysis and recommendations. It goes beyond a simple read or write operation by orchestrating an interactive session. It may also write project configuration as a side effect of setup, making Execute the most appropriate category given the active process execution involved.
From the tool's definition "Run interactive wizard for project setup" and "Guides through questions to gather requirements and can recommend AI analysis for stack selection"
Attacks that exploit this kind of access
Run interactive wizard for project setup. Guides through questions to gather requirements and can recommend AI analysis for stack selection. It is categorised as a Execute tool in the Gigaspec MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gigaspec MCP server in PolicyLayer and add a rule for gigaspec-wizard: 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 Gigaspec. Nothing to install.
gigaspec-wizard is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gigaspec-wizard 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 gigaspec-wizard. 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.
gigaspec-wizard is provided by the Gigaspec MCP server (oleksiitrembach/gigaspec). 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 →