render_get_service
Get details for a specific Render service.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/render-get-service.md
What render_get_service does on UnClick
AI agents call render_get_service to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | — | |
service_id | string | Yes | Render service ID (srv-...) |
Parameters from the server's own tool schema.
Why render_get_service is rated Low
The verb 'Get' and the action of retrieving service details constitute a read-only operation that queries configuration or state information without side effects. This is a straightforward data retrieval with no capability to modify, execute, or destroy resources.
From the tool's definition Tool name 'render_get_service' and description 'Get details for a specific Render service' indicate a retrieval operation with no modification or deletion.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs render_get_service safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_get_service, this is the rule to start with:
render_get_service is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every render_get_service call is checked against it from then on.
Questions about render_get_service
Get details for a specific Render service. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
render_get_service accepts 2 parameters: api_key, service_id. Required: service_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for render_get_service: 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 UnClick. Nothing to install.
render_get_service 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 render_get_service 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 render_get_service. 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.
render_get_service is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue