List the supported ASN.1 Instance Builder subset, JSON input shapes, and known limitations.
AI agents call list_asn1_builder_features to retrieve information from PKI Studio MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents metadata about ASN.1 builder capabilities. It does not create, modify, delete, execute code, or incur financial obligations. It is a straightforward Read operation that provides reference documentation about supported features.
From the tool's definition "List the supported ASN.1 Instance Builder subset, JSON input shapes, and known limitations." The verb "List" and the purely informational nature of the output (enumerating features, input shapes, and limitations) indicate data retrieval with no side effects.
Attacks that exploit this kind of access
List the supported ASN.1 Instance Builder subset, JSON input shapes, and known limitations. It is categorised as a Read tool in the PKI Studio MCP MCP Server, which means it retrieves data without modifying state.
Register the PKI Studio MCP server in PolicyLayer and add a rule for list_asn1_builder_features: 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 PKI Studio MCP. Nothing to install.
list_asn1_builder_features 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 list_asn1_builder_features 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 list_asn1_builder_features. 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.
list_asn1_builder_features is provided by the PKI Studio MCP server (pkistudio/pkistudiomcp). 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 →