Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool.
AI agents call microcms_get_api_info to retrieve information from microCMS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves API schema information from microCMS Management API. It is a read-only operation that fetches metadata about API structure (relation and relationList fields). There are no mutations, deletions, executions, or financial implications.
From the tool's definition Tool name contains 'get' and description states 'Get API schema information' — retrieves schema metadata without modifying data. No side effects or state changes.
Documented attack patterns abuse exactly the kind of access microcms_get_api_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and microCMS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for microcms_get_api_info:
{
"version": "1",
"default": "deny",
"tools": {
"microcms_get_api_info": {}
}
} microcms_get_api_info 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.
Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool. It is categorised as a Read tool in the microCMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the microCMS MCP Server MCP server in PolicyLayer and add a rule for microcms_get_api_info: 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 microCMS MCP Server. Nothing to install.
microcms_get_api_info 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 microcms_get_api_info 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 microcms_get_api_info. 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.
microcms_get_api_info is provided by the microCMS MCP Server MCP server (microcmsio/microcms-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from microCMS MCP Server, 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.
14 microCMS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.