This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ram-get-character.md
What ram_get_character does on UnClick
AI agents call ram_get_character 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 |
|---|---|---|---|
id | string | Yes | Character ID |
Parameters from the server's own tool schema.
Why ram_get_character is rated Low
This tool retrieves character data from what appears to be a Rick and Morty API by ID lookup. The verb 'Get' and lack of any modification, deletion, or execution language confirm this is a simple read operation. No data is modified, deleted, or executed. Blast radius is minimal—worst case, an agent retrieves unwanted character data.
From the tool's definition Tool name 'ram_get_character' and description 'Get a Rick and Morty character by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs ram_get_character 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 ram_get_character, this is the rule to start with:
ram_get_character 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 ram_get_character call is checked against it from then on.
Questions about ram_get_character
Get a Rick and Morty character by ID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
ram_get_character accepts 1 parameter: id. Required: 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 ram_get_character: 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.
ram_get_character 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 ram_get_character 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 ram_get_character. 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.
ram_get_character 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