Call this tool to get a article for tech blog, tech document, 기술 문서, 기술 글. * Instruction: - 의미없는 일반적인 값은 빈값으로 처리. 예> 최신/최근 글, 최신/최근 문서 * Parameters: - query: Keyword * Return Schema: [ { "title": "string", "date": "YYYY-MM-DD", "url": "string" } ]
Accepts freeform code/query input (query)
Part of the Cloud101 Korea MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call Tech_Blog to retrieve information from Cloud101 Korea without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though Tech_Blog only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
Tech_Blog:
rules:
- action: allowSee the full Cloud101 Korea policy for all 3 tools.
Agents calling read-class tools like Tech_Blog have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Call this tool to get a article for tech blog, tech document, 기술 문서, 기술 글. * Instruction: - 의미없는 일반적인 값은 빈값으로 처리. 예> 최신/최근 글, 최신/최근 문서 * Parameters: - query: Keyword * Return Schema: [ { "title": "string", "date": "YYYY-MM-DD", "url": "string" } ]. It is categorised as a Read tool in the Cloud101 Korea MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for Tech_Blog. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cloud101 Korea MCP server.
Tech_Blog 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 Tech_Blog rule in your Intercept 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 Intercept policy for Tech_Blog. 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.
Tech_Blog is provided by the Cloud101 Korea MCP server (cloud101.kr/cloud101kr). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept