서비스 목록을 조회합니다.
AI agents call getServices to retrieve information from API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of services without modifying, deleting, or executing any operations. It is a straightforward data retrieval operation analogous to 'list' or 'get', which falls under the Read category. The severity is low because querying a service list poses minimal security risk unless the list itself contains sensitive data, but standard API service listings are typically non-sensitive metadata.
From the tool's definition Tool name 'getServices' with description '서비스 목록을 조회합니다' (translates to 'Retrieve/query service list'). The verb '조회' means 'to query' or 'to retrieve', indicating a read-only operation with no side effects.
Attacks that exploit this kind of access
서비스 목록을 조회합니다. It is categorised as a Read tool in the API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the API MCP Server MCP server in PolicyLayer and add a rule for getServices: 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 API MCP Server. Nothing to install.
getServices 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 getServices 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 getServices. 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.
getServices is provided by the API MCP Server MCP server (koseha/api-mcp). 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 →