Export current proxy configuration to file
AI agents use proxy_export_config to create or update resources in Web Proxy MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Web Proxy MCP Server environment.
This tool writes configuration data to a file, making it a Write operation. The severity is medium because exported configs may contain sensitive information (credentials, routing rules, authentication details), but the operation is reversible and does not execute code or cause destructive changes.
From the tool's definition Tool name 'proxy_export_config' and description 'Export current proxy configuration to file' indicate creation/output of configuration data to persistent storage.
Attacks that exploit this kind of access
Export current proxy configuration to file. It is categorised as a Write tool in the Web Proxy MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Web Proxy MCP Server MCP server in PolicyLayer and add a rule for proxy_export_config: 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 Web Proxy MCP Server. Nothing to install.
proxy_export_config 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 proxy_export_config 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 proxy_export_config. 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.
proxy_export_config is provided by the Web Proxy MCP Server MCP server (mako10k/mcp-web-proxy). 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 →