hourly_rate
Freelancer Hourly Rate Calculator — Back the hourly rate a freelancer must charge from target take-home income, overhead, billable %, and tax buffer.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/hourly-rate.md
What hourly_rate does on Gateway
AI agents call hourly_rate to retrieve information from Gateway 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 |
|---|---|---|---|
billable_pct | number | — | Percent of worked hours that are billable (e.g. 60) |
weeks_worked | number | — | Weeks worked per year |
target_income | number | Yes | Desired annual take-home income in USD |
hours_per_week | number | — | Hours worked per week |
tax_buffer_pct | number | — | Percent set aside for taxes |
annual_overhead | number | — | Annual business overhead in USD |
Parameters from the server's own tool schema.
Why hourly_rate is rated Low
This is a pure computational tool that takes parameters and returns a calculated result. It retrieves/computes information without side effects, matching the Read category. The severity is low as misuse would only produce incorrect calculations, not expose sensitive data or cause harm.
From the tool's definition Tool performs calculation-based analysis ('Calculator', 'Back the hourly rate') with inputs (target income, overhead, billable %, tax buffer) to derive an output.
Attacks that exploit this kind of access
The rule that runs hourly_rate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hourly_rate, this is the rule to start with:
hourly_rate 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 Gateway, apply this rule, and every hourly_rate call is checked against it from then on.
Questions about hourly_rate
Freelancer Hourly Rate Calculator — Back the hourly rate a freelancer must charge from target take-home income, overhead, billable %, and tax buffer. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
hourly_rate accepts 6 parameters: billable_pct, weeks_worked, target_income, hours_per_week, tax_buffer_pct, annual_overhead. Required: target_income. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for hourly_rate: 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 Gateway. Nothing to install.
hourly_rate 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 hourly_rate 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 hourly_rate. 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.
hourly_rate is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue