AI agents invoke generate_coupang_deeplink to trigger actions in Coupang MCP. 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.
This tool calls an external service to transform a URL into a deeplink/shortened link. It's not a pure read (it creates/generates a new resource), and it triggers an external operation whose output depends on the input URL. It falls under Execute as it involves calling an external API or service to produce a transformed artifact, rather than simply querying existing data.
From the tool's definition '쿠팡 상품 URL을 단축 링크로 변환합니다' (Converts Coupang product URL to a shortened link) — triggers an external URL shortening/deeplink generation operation
Documented attack patterns abuse exactly the kind of access generate_coupang_deeplink gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coupang MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_coupang_deeplink:
{
"version": "1",
"default": "deny",
"tools": {
"generate_coupang_deeplink": {
"limits": [
{
"counter": "generate_coupang_deeplink_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_coupang_deeplink stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
쿠팡 상품 URL을 단축 링크로 변환합니다. It is categorised as a Execute tool in the Coupang MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Coupang MCP server in PolicyLayer and add a rule for generate_coupang_deeplink: 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 Coupang MCP. Nothing to install.
generate_coupang_deeplink 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 generate_coupang_deeplink 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 generate_coupang_deeplink. 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.
generate_coupang_deeplink is provided by the Coupang MCP server (uju777/coupang-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coupang MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Coupang MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.