Agent Posture
The Agent Posture tab configures thresholds and rate-limit parameters that govern MCP (Model Context Protocol) server behavior. These settings are used when evaluating agent posture health. This tab is accessible to System Admin users only.
| Setting | Description |
|---|---|
| Unused MCP Threshold (days) | Number of days after which an MCP server that has not been used is flagged as inactive in posture assessments. Valid range: 1–999 days. |
| MCP Rate Limit – Calls per Minute | Maximum number of calls allowed to an MCP server within a one-minute window. Valid range: 1–9,999 calls per minute. |
| MCP Rate Limit – Calls per Hour | Maximum number of calls allowed to an MCP server within a one-hour window. Valid range: 1–99,999 calls per hour. |
Unused MCP Threshold
When an MCP server connected to an agent goes unused for longer than the configured threshold, Agent Identity Security creates a posture finding. This helps you identify stale or abandoned MCP connections that expand your attack surface without providing value.
Set this value based on the normal usage pattern of your environment. A threshold of 7 days is appropriate for actively used agents. For agents that run on a weekly or monthly schedule, increase the threshold to avoid false positives.
MCP Rate Limits
Rate limits control how many API calls Agent Identity Security allows per MCP server within a time window. They protect downstream MCP servers from being overwhelmed by agent activity and help you detect unusual call volumes that may indicate a misbehaving or compromised agent.
If a legitimate agent regularly exceeds the default limits, increase the values to match its normal operating pattern. Investigate before raising limits high call volumes may indicate a posture issue rather than a configuration gap.
Changes take effect after you click Save Changes.
