get_usage

get_usage

Server SwipeBuilder MCP Server swipebuilder-io/swipebuilder-mcp
Category Read
Risk class Low
Parameters 00 required

What get_usage does on SwipeBuilder MCP Server

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

Why get_usage needs a policy

This tool retrieves usage/credit information with no side effects. The server description explicitly describes usage monitoring as a Read operation (no modifications). Empty tool description lowers confidence slightly, but the context from sibling tools (all get_* retrieval operations) and parent server description strongly support Read classification.

From the tool's definition Tool name 'get_usage' combined with server description stating it 'provides tools to monitor API credit usage through natural language' indicates a read-only retrieval of usage metrics.

Questions about get_usage

What does the get_usage tool do? +

get_usage. It is categorised as a Read tool in the SwipeBuilder MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_usage? +

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

What risk level is get_usage? +

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

Can I rate-limit get_usage? +

Yes. Add a rate_limit block to the get_usage 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_usage completely? +

Set action: deny in the PolicyLayer policy for get_usage. 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_usage? +

get_usage is provided by the SwipeBuilder MCP Server MCP server (swipebuilder-io/swipebuilder-mcp). 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.