Check admission status using CNIC.
AI agents call check_admission_status to retrieve information from UAAR University MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation—it queries and returns admission status data based on a CNIC identifier. No data is created, modified, deleted, or executed. The operation has minimal security blast radius since it retrieves only status information that applicants would typically have authorized access to view. It is categorized as Read with low severity.
From the tool's definition Tool name 'check_admission_status' and description 'Check admission status using CNIC' indicate a query/lookup operation that retrieves existing admission information without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access check_admission_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UAAR University MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_admission_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_admission_status": {}
}
}check_admission_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check admission status using CNIC. It is categorised as a Read tool in the UAAR University MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UAAR University MCP Server MCP server in PolicyLayer and add a rule for check_admission_status: 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 UAAR University MCP Server. Nothing to install.
check_admission_status 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 check_admission_status 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 check_admission_status. 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.
check_admission_status is provided by the UAAR University MCP Server MCP server (saramali15792/instituaionmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UAAR University MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
53 UAAR University MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.