Set a specific environment variable in an app\
AI agents use faber_set_env_var to create or update resources in Faber MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Faber MCP Server environment.
This tool creates or modifies environment variables in a deployed application. While reversible (variables can be changed or deleted), it affects application behavior and could expose sensitive data if misused (database credentials, API keys, etc.).
From the tool's definition Tool name 'faber_set_env_var' and description 'Set a specific environment variable in an app' indicate modification of application configuration state. Environment variables are data that are created or modified reversibly.
Attacks that exploit this kind of access
Set a specific environment variable in an app\. It is categorised as a Write tool in the Faber MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Faber MCP Server MCP server in PolicyLayer and add a rule for faber_set_env_var: 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 Faber MCP Server. Nothing to install.
faber_set_env_var 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 faber_set_env_var 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 faber_set_env_var. 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.
faber_set_env_var is provided by the Faber MCP Server MCP server (joshtrebilco/faber-mcp). 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 →