get

Get value by key from Redis

Server Server Puppeteer @hisma/server-puppeteer
Category Read
Risk class Low
Parameters 00 required

What get does on Server Puppeteer

AI agents call get to retrieve information from Server Puppeteer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get needs a policy

The 'get' operation retrieves data from Redis by key. This is a read-only query that does not modify, delete, or execute any operations. Even though Redis can contain sensitive data, the tool itself only performs a retrieval operation, which is the defining characteristic of the Read category.

From the tool's definition Tool name 'get' and description 'Get value by key from Redis' indicate a retrieval operation with no side effects.

Questions about get

What does the get tool do? +

Get value by key from Redis. It is categorised as a Read tool in the Server Puppeteer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get? +

Register the Server Puppeteer MCP server in PolicyLayer and add a rule for get: 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 Server Puppeteer. Nothing to install.

What risk level is get? +

get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get? +

Yes. Add a rate_limit block to the get 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.

How do I block get completely? +

Set action: deny in the PolicyLayer policy for get. 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.

What MCP server provides get? +

get is provided by the Server Puppeteer MCP server (@hisma/server-puppeteer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.