Add a new target domain for proxy monitoring
AI agents use proxy_add_target 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 creates a new configuration record (a monitoring target) in the proxy system. While it modifies system state by adding a target domain, it is reversible (targets can typically be removed), does not execute arbitrary code or commands, and does not delete data. This makes it a Write operation.
From the tool's definition Tool name 'proxy_add_target' and description 'Add a new target domain for proxy monitoring' indicate creation of a new monitoring configuration entry.
Attacks that exploit this kind of access
Add a new target domain for proxy monitoring. 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_add_target: 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_add_target 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_add_target 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_add_target. 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_add_target 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 →