enable_login_gate
Turn on an optional passcode gate for the project
This record as markdown: /tools/ai-featureboard-featureboard/enable-login-gate.md
What enable_login_gate does on FeatureBoard
AI agents use enable_login_gate to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why enable_login_gate is rated Medium
This tool creates or modifies project settings (enabling a login gate) reversibly—the gate can be disabled later. It is not reading data (Read), executing arbitrary code (Execute), permanently destructive (Destructive), or financial (Financial). The action is reversible and represents a configuration change, fitting the Write category.
From the tool's definition Tool name is 'enable_login_gate' and description states it will 'Turn on an optional passcode gate for the project', indicating it modifies project configuration by enabling a security feature.
Attacks that exploit this kind of access
The rule that runs enable_login_gate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_login_gate, this is the rule to start with:
enable_login_gate 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 FeatureBoard, apply this rule, and every enable_login_gate call is checked against it from then on.
Questions about enable_login_gate
Turn on an optional passcode gate for the project. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for enable_login_gate: 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 FeatureBoard. Nothing to install.
enable_login_gate 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 enable_login_gate 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 enable_login_gate. 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.
enable_login_gate is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue