create_meterreadings_rentals_summary
This endpoint can be used to both create and update a meter reading detail for a property.\r\n <ul><li>There can only be one meter reading detail for a given combination of MeterType and ReadingDate for a property.</li><li>If you are updating an existing meter reading detail, use the query parame...
This record as markdown: /tools/wpm-mcp-server/create-meterreadings-rentals-summary.md
What create_meterreadings_rentals_summary does on Wpm Mcp Server
AI agents use create_meterreadings_rentals_summary to create or update resources in Wpm Mcp Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wpm Mcp Server environment.
Why create_meterreadings_rentals_summary is rated Medium
This tool creates and modifies meter reading records for properties, which are data changes that are reversible (meter readings can be updated or corrected). It falls under Write category rather than Execute/Destructive because it only creates/modifies structured data records.
From the tool's definition Tool name contains 'create' and description states 'This endpoint can be used to both create and update a meter reading detail for a property.' The description explicitly indicates the endpoint creates new meter reading details and updates existing ones.
Attacks that exploit this kind of access
The rule that runs create_meterreadings_rentals_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wpm Mcp Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_meterreadings_rentals_summary, this is the rule to start with:
create_meterreadings_rentals_summary stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wpm Mcp Server, apply this rule, and every create_meterreadings_rentals_summary call is checked against it from then on.
Questions about create_meterreadings_rentals_summary
This endpoint can be used to both create and update a meter reading detail for a property.\r\n <ul><li>There can only be one meter reading detail for a given combination of MeterType and ReadingDate for a property.</li><li>If you are updating an existing meter reading detail, use the query parameters to specify the existing meter reading detail to update.</li><li>If you are creating a new meter reading detail, do not pass any query parameters.</li><li>When adding a new item to the Details array, leave out the. It is categorised as a Write tool in the Wpm Mcp Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for create_meterreadings_rentals_summary: 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 Wpm Mcp Server. Nothing to install.
create_meterreadings_rentals_summary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_meterreadings_rentals_summary 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 create_meterreadings_rentals_summary. 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.
create_meterreadings_rentals_summary is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wpm Mcp Server, and thousands of servers like it.
This server
Across the catalogue