identity_get_token_vault
AI agents call identity_get_token_vault as a supporting operation in AWS IoT SiteWise MCP Server workflows.
With no description available, classification relies solely on the tool name. 'identity_get_token_vault' implies fetching or retrieving token vault credentials, which would be a Read operation. However, if misused, credential retrieval could have security implications. Confidence is low due to the empty description. Assigning 'Other' given the ambiguity, but this warrants further investigation.
From the tool's definition Tool description is empty and uninformative; the name 'identity_get_token_vault' suggests a read/retrieval operation on identity tokens or credentials.
Attacks that exploit this kind of access
identity_get_token_vault. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for identity_get_token_vault: 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 AWS IoT SiteWise MCP Server. Nothing to install.
identity_get_token_vault is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the identity_get_token_vault 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 identity_get_token_vault. 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.
identity_get_token_vault is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.