AI agents call fetch to retrieve information from YiGmMk/mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reads web content from a URL using the Jina.ai reader service. It is a straightforward read operation with no side effects—it does not modify data, execute code, delete resources, or commit financial actions. The blast radius of misuse is limited to potentially accessing unintended web content or making requests to arbitrary URLs, which poses minimal security risk.
From the tool's definition Tool description states '使用 r.jina.ai 读取 URL 并获取其内容' which translates to 'use r.jina.ai to read URL and get its content'. The verb '读取' (read) and '获取' (fetch/retrieve) indicate data retrieval without modification or execution.
Documented attack patterns abuse exactly the kind of access fetch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YiGmMk/mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch:
{
"version": "1",
"default": "deny",
"tools": {
"fetch": {}
}
}fetch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
使用 r.jina.ai 读取 URL 并获取其内容. It is categorised as a Read tool in the YiGmMk/mcp MCP Server, which means it retrieves data without modifying state.
Register the YiGmMk/ MCP server in PolicyLayer and add a rule for fetch: 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 YiGmMk/mcp. Nothing to install.
fetch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fetch 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 fetch. 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.
fetch is provided by the YiGmMk/ MCP server (yigmmk/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from YiGmMk/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.
4 YiGmMk/mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.