Configure Rezdy Agent API connection with API key and environment
AI agents use rezdy_agent_configure to create or update resources in Rezdy Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rezdy Agent MCP Server environment.
Configuring API connections involves storing sensitive credentials (API key) and changing environment settings, which are reversible write operations. This is classified as Write rather than Execute because configuration modification is the direct action, not triggering code execution.
From the tool's definition Tool name is 'rezdy_agent_configure' and description states it 'Configure[s] Rezdy Agent API connection with API key and environment' — this modifies configuration state by storing/setting API credentials and environment parameters.
Attacks that exploit this kind of access
Configure Rezdy Agent API connection with API key and environment. It is categorised as a Write tool in the Rezdy Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rezdy Agent MCP Server MCP server in PolicyLayer and add a rule for rezdy_agent_configure: 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 Rezdy Agent MCP Server. Nothing to install.
rezdy_agent_configure 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 rezdy_agent_configure 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 rezdy_agent_configure. 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.
rezdy_agent_configure is provided by the Rezdy Agent MCP Server MCP server (jezweb/rezdy-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →